Security Resilience

CVE-2026-120637

Published
04 November 2026
Modified
09 November 2026
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0053 45th percentile
Risk Priority 71 floored blend · peak EPSS

CVSS 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-120637 is a critical-severity Active Debug Code (CWE-489) vulnerability. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Office Test (T1137.002); ranked at the 45th 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 CM-2 (Baseline Configuration) and CM-7 (Least Functionality) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

CGI versions before 5.00 for Perl take request parameters from the process command line arguments for an unrecognised REQUEST_METHOD. For a REQUEST_METHOD such as OPTIONS, CGI falls through to its offline debugging mode, which is on by default, and builds…

more

the parameters and path_info from the process's command line arguments.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1137.002 Office Test Persistence
Adversaries may abuse the Microsoft Office "Office Test" Registry key to obtain persistence on a compromised system.
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.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
T1584.004 Server Resource Development
Adversaries may compromise third-party servers that can be used during targeting.
T1584.008 Network Devices Resource Development
Adversaries may compromise third-party network devices that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-42872Shared CWE-489
CVE-2026-81943Shared CWE-489
CVE-2023-22357Shared CWE-489
CVE-2026-9133Shared CWE-489
CVE-2024-21785Shared CWE-489
CVE-2024-31406Shared CWE-489
CVE-2024-29075Shared CWE-489
CVE-2024-30219Shared CWE-489
CVE-2025-52663Shared CWE-489
CVE-2026-54798Shared CWE-489

Affected Assets

—
CGI
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Baseline configuration defines the approved production state that must exclude active debug code.

Least functionality explicitly prohibits enabling unnecessary debug or diagnostic features in production builds.

Documented development standards and tools can require removal of debug code before release.

Security-integrated SDLC processes ensure debug artifacts are stripped prior to deployment.

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.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require removal of debug code before release, covering most of this weakness while the control addresses many other development issues.

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.

finds

Security testing in development and acceptance catches active debug code before deployment.

blocks

Configuration management can disable or remove debug features through hardened baselines.

finds

A.5.21's guidance item (f) explicitly includes penetration testing of delivered ICT products as a validation method, and item (i) seeks assurance products function without unwanted features — both can surface externally accessible debug interfaces or backdoors. However, the control's primary mechanism is supply-chain governance (contractual requirements, attestations, monitoring for tampering), and most active debug code is internal code paths or configuration that runtime testing does not reach; the control does not mandate source review of supplier code, so the share of latent instances found is a minority.

blocks

A.8.20's firewalls, network authentication and segregation can block external network access to debug interfaces, denying the attacker use of the weakness over part of the path, but the debug code remains present and exploitable from within the network or via any interface the controls do not reach.

prevents

Secure coding standards explicitly prohibit leaving debug code active in production.

finds

A.8.30's programme requires the supplier to implement secure development and testing practices (8.25–8.29), acceptance testing, and evidence of testing for malicious content and known vulnerabilities, which would surface active debug code through SAST, code review, and acceptance testing; however, the clause is a contractual/process control whose effect is mediated through supplier compliance and evidence documentation rather than direct testing, so only a minority of instances are reliably found.

References