Security Resilience

CVE-2026-86255

DoS

Public PoCDoS
Published
06 September 2026
Modified
18 September 2026
CVSS Score v4 7.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/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.0044 37th percentile
Risk Priority 36 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-86255 is a high-severity Uncontrolled Resource Consumption (CWE-400) vulnerability. Its CVSS base score is 7.1 (High).

Operationally, ranked at the 37th 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 SC-5 (Denial-of-service Protection) and SC-6 (Resource Availability) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

wger before 2.5 fails to validate the maximum duration of routine date ranges, allowing authenticated users to create routines spanning arbitrarily long periods. Attackers can trigger the date_sequence computation via routine detail endpoints, forcing the server to iterate thousands of…

more

times per request and exhaust worker threads, denying service to legitimate users.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-45196Shared CWE-400
CVE-2023-3614Shared CWE-400
CVE-2025-25293Shared CWE-400
CVE-2023-28188Shared CWE-400
CVE-2026-101901Shared CWE-400
CVE-2026-28375Shared CWE-400
CVE-2024-1635Shared CWE-400
CVE-2023-32787Shared CWE-400
CVE-2022-4986Shared CWE-400
CVE-2023-31418Shared CWE-400

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-5 directly limits the effects of resource-exhaustion events that constitute uncontrolled consumption.

SC-6 enforces explicit allocation limits on resources, structurally preventing the weakness from occurring.

Process isolation confines resource consumption to separate domains, reducing blast radius without stopping the root flaw.

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.

finds

Resource-utilization monitoring and alerting on bottlenecks or overloads limits the impact of denial-of-service or resource-exhaustion attacks.

blocks

A.8.6's monitoring, stress-testing, projections, tuning, demand-reduction steps (e.g. optimizing queries, deleting obsolete data, restricting non-critical bandwidth) and capacity planning directly stop most uncontrolled consumption from being exploitable by keeping resources within safe bounds; the bounded remainder is algorithmic flaws (e.g. infinite loops, uncontrolled recursion) that no amount of capacity planning can prevent from exhausting a resource when triggered.

finds

Early notification of anomalous resource consumption or system malfunctions enables throttling or isolation before availability is lost.

blocks

Monitoring network service usage and applying controls to restrict access when necessary limits an attacker’s ability to consume excessive resources through unrestricted or unauthenticated service calls.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-400, a class-level weakness. Rules are authored against its narrower children: CWE-770.

References