Cyber Resilience

CVE-2026-62673

Published
19 August 2026
Modified
21 August 2026
CVSS Score v4 8.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0040 34th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2026-62673 is a high-severity Improper Handling of Case Sensitivity (CWE-178) vulnerability. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Masquerading (T1036); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Grav is a file-based Web platform. Prior to 2.0.4, the Grav .htaccess and webserver-configs/htaccess.txt security rules omit the Apache [NC] flag and therefore compare sensitive directory and file-extension patterns case-sensitively. On a case-insensitive filesystem, an unauthenticated requester can use uppercase…

more

directory or extension variants to bypass the rules and retrieve files under user/accounts or user/config, including password hashes and security configuration. This issue is fixed in version 2.0.4.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1036 Masquerading Stealth
Adversaries may attempt to manipulate features of their artifacts to make them appear legitimate or benign to users and/or security tools.
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.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-46701Shared CWE-178
CVE-2024-38829Shared CWE-178
CVE-2026-15617Shared CWE-178
CVE-2026-54528Shared CWE-178
CVE-2026-32939Shared CWE-178
CVE-2026-33691Shared CWE-178
CVE-2021-24347Shared CWE-178
CVE-2023-3545Shared CWE-178
CVE-2026-62230Shared CWE-178
CVE-2025-4035Shared CWE-178

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Applying access control decisions to each request depends on accurate property determination that accounts for case differences.

Correct enforcement of authorizations for resource access structurally requires consistent case-sensitive handling of identifiers to avoid incorrect decisions.

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 partial match
prevents

Secure SDLC practices can catch and prevent case-sensitivity flaws during code review or testing, but fixing one CWE achieves negligible coverage of the broad control.

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.

prevents

Secure SDLC practices should include case-sensitivity requirements in design and coding standards.

prevents

Application security requirements must specify case handling for identifiers and paths.

prevents

Architecture principles should enforce canonical, case-aware resource naming.

prevents

Secure coding guidelines must mandate explicit case handling to prevent inconsistent lookups.

degrades

Access-control rules that ignore case can allow unintended resource access.

degrades

Authentication logic must treat identifiers consistently to avoid bypass via case differences.

References