Cyber Resilience

CVE-2026-44837

Viewcomponent View Component 3.0.0 – 4.9.0

Public PoC
Published
26 May 2026
Modified
24 July 2026
Patch / advisory
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0041 34th percentile
Risk Priority 46 floored blend · peak EPSS

Summary

CVE-2026-44837 is a medium-severity Partial String Comparison (CWE-187) vulnerability in Viewcomponent View Component. Its CVSS base score is 5.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

No EU or UK CSIRT advisories indexed for this CVE.

Vulnerability Data

view_component is a framework for building reusable, testable, and encapsulated view components in Ruby on Rails. From 3.0.0 to 4.9.0, the system test entrypoint canonicalizes a user-controlled file path with File.realpath, then checks whether the resolved path starts with the…

more

temp directory path. This is not a safe containment check because sibling directories can share the same string prefix. This vulnerability is fixed in 4.9.0.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-21636Same product: Viewcomponent View Component
CVE-2026-54498Same product: Viewcomponent View Component
CVE-2026-54497Same product: Viewcomponent View Component
CVE-2025-23384Shared CWE-187
CVE-2026-55602Shared CWE-187
CVE-2024-39742Shared CWE-187
CVE-2026-14687Shared CWE-187
CVE-2026-45692Shared CWE-187
CVE-2026-35031Shared CWE-187
CVE-2024-41110Shared CWE-187

Affected Assets

viewcomponent
view component
3.0.0 — 4.9.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V10.4.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover incomplete string comparisons through targeted test cases.

Access enforcement depends on correct authorization checks; partial comparisons would violate the required enforcement of full authorizations.

Security engineering principles include correct and complete comparison logic to avoid flawed decision points.

Input validation requirements force complete rather than partial string comparisons before decisions are made.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent unsafe string comparisons by enforcing proper API usage and testing.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover partial-comparison flaws during code or binary analysis.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect and prevent partial string comparison flaws before deployment.

prevents

Secure development lifecycle practices can include requirements to avoid partial string comparisons in authentication or validation logic.

prevents

Application security requirements can mandate full, exact comparisons for sensitive operations.

degrades

Secure system architecture principles discourage unsafe partial comparisons in critical paths.

prevents

Secure coding standards can explicitly prohibit substring-based comparisons for security decisions.

degrades

Secure authentication mechanisms can reduce reliance on partial string comparisons for credential or token validation.

References