CVE-2026-36453
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-36453 is a high-severity Forced Browsing (CWE-425) vulnerability in Rhymix (inferred from references). Its CVSS base score is 7.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 19th 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.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-77109
Vulnerability Data
Rhymix before 2.1.31 allows insecure direct object reference, aka RVE-2026-1. Arbitrary files can be accessed via extra variables.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
AC-24 requires that access-control decisions be applied to every request, addressing the missing enforcement on restricted URLs.
AC-3 directly requires enforcement of authorizations for access to resources such as URLs, scripts, and files, structurally preventing forced browsing.
AC-6 requires restricting authorizations to the minimum needed, reducing the set of resources that must be protected against direct requests.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.3 mandates access controls on information in systems, applications and services (guidance items b, c, d), and when applied to a web application with CWE-425 flaws, requires authorization checks on all restricted URLs/scripts/files, removing the weakness.
Security testing can detect forced-browsing flaws, but the control itself does not prevent them in production.
Secure coding practices reduce the likelihood of missing authorization checks, yet do not guarantee coverage.
A.8.8's reach is DISCLOSURE — it sees vulnerabilities through published advisories, vendor CVE feeds, and scanning against known-flaw inventories. CWE-425 (forced browsing) does surface as CVEs (multiple examples in the CWE entry), so the disclosed minority is reachable, but the bulk of forced-browsing instances are first-party authorization flaws in custom web applications that never receive a CVE and are outside A.8.8's disclosure-based reach.