Cyber Resilience

CVE-2026-75840

Public PoC
Published
18 August 2026
Modified
18 August 2026
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/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.0031 24th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2026-75840 is a high-severity Comparison Using Wrong Factors (CWE-1025) vulnerability. Its CVSS base score is 8.7 (High).

Operationally, ranked at the 24th 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 SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

ArcadeDB before 26.8.1 contains an arbitrary file read vulnerability in the GraalVM JavaScript sandbox allowlist enforcement, which uses unescaped regular expressions to validate package names. Attackers with trigger creation privileges can use Java.type() to access java.util.zip.ZipFile or java.util.jar.JarFile classes and…

more

read arbitrary files on the host system as the ArcadeDB server process.

CWE(s)
CWE-1025

Related Threats

CVEs Like This One

CVE-2024-20342Shared CWE-1025
CVE-2026-40227Shared CWE-1025
CVE-2025-71377Shared CWE-1025
CVE-2026-9800Shared CWE-1025
CVE-2025-2887Shared CWE-1025
CVE-2025-32464Shared CWE-1025
CVE-2025-27839Shared CWE-1025
CVE-2025-2888Shared CWE-1025
CVE-2026-40880Shared CWE-1025
CVE-2026-48860Shared CWE-1025

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover incorrect comparison logic after implementation but does not stop the flaw from being written.

SA-15 Development Process, Standards, and Tools partial match

Requiring a documented development process and tools can embed standards that reduce introduction of erroneous comparison factors.

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 activities such as code review and logic testing directly prevent incorrect comparison factors in code.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect incorrect comparison results during development and acceptance.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes requirements and reviews that can catch incorrect comparison logic.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify correct comparison criteria and validation rules.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address proper comparison logic and factor selection.

References