Security Resilience

CVE-2026-115727

Public PoC
Published
23 October 2026
Modified
23 October 2026
CVSS Score v4 9.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:H/VA:H/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.0070 53th percentile
Risk Priority 47 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-115727 is a critical-severity Active Debug Code (CWE-489) vulnerability. Its CVSS base score is 9.2 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Office Test (T1137.002); ranked in the top 47% of CVEs by exploit likelihood; 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 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

AgenticSeek before commit 409840c contains a remote code execution vulnerability because llm_server/app.py hardcodes Flask debug mode while binding to all interfaces. Attackers who reach the server port and obtain the derivable Werkzeug debugger PIN can execute Python code and operating…

more

system commands with llm_server privileges.

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-2024-32047Shared CWE-489
CVE-2026-59092Shared CWE-489
CVE-2026-81943Shared CWE-489
CVE-2026-84486Shared CWE-489
CVE-2023-21496Shared CWE-489
CVE-2026-83550Shared CWE-489
CVE-2023-49593Shared CWE-489
CVE-2024-31406Shared CWE-489
CVE-2024-21827Shared CWE-489
CVE-2025-52663Shared CWE-489

Affected Assets

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.

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.

blocks

Change management can enforce removal of debug code as part of release gates.

References