Security Resilience

CVE-2026-72914

DoS

Published
10 August 2026
Modified
09 September 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0083 58th percentile
Risk Priority 59 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-72914 is a high-severity Amplification (CWE-405) vulnerability. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique SMS Pumping (T1496.003); ranked in the top 42% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-10 (Concurrent Session Control) and SC-5 (Denial-of-service Protection) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Mastodon is a free, open-source social network server based on ActivityPub. Prior to 4.4.21, 4.5.14, 4.6.4, and 4.7.0-beta.1, the administrative statistics endpoints handled by Api::V1::Admin::MeasuresController and Api::V1::Admin::RetentionController checked authorization only after beginning expensive calculations. Anonymous callers could submit keys, start_at,…

more

and end_at parameters that caused long-running SQL queries in Admin::Metrics::Measure, Admin::Metrics::Retention, and Admin::Metrics::Dimension::BaseDimension, allowing repeated requests to exhaust server resources. This issue is fixed in versions 4.4.21, 4.5.14, 4.6.4, and 4.7.0-beta.1.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1496.003 SMS Pumping Impact
Adversaries may leverage messaging services for SMS pumping, which may impact system and/or hosted service availability.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.001 OS Exhaustion Flood Impact
Adversaries may launch a denial of service (DoS) attack targeting an endpoint's operating system (OS).
T1499.002 Service Exhaustion Flood Impact
Adversaries may target the different network services provided by systems to conduct a denial of service (DoS).
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-34703Shared CWE-405, CWE-770
CVE-2026-125327Shared CWE-405, CWE-770
CVE-2026-45557Shared CWE-405, CWE-770
CVE-2026-47774Shared CWE-405, CWE-770
CVE-2023-30903Shared CWE-770
CVE-2024-55195Shared CWE-770
CVE-2024-50311Shared CWE-770
CVE-2026-128340Shared CWE-770
CVE-2025-21492Shared CWE-770
CVE-2024-12705Shared CWE-770

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 5 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Directly enforces a hard limit on concurrent sessions, structurally preventing unbounded resource allocation.

SC-5 directly requires mechanisms to limit the effects of asymmetric resource exhaustion attacks such as amplification DoS.

SC-6 enforces resource quotas and priority allocation that reduce the impact of unauthenticated or low-effort resource requests.

Imposes a limit on consecutive invalid attempts, preventing one specific class of unbounded resource consumption.

Least-functionality disables unnecessary services or features that could be leveraged for amplification.

SC-7 boundary controls can filter or rate-limit traffic patterns that enable amplification without equivalent client work.

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.IR-04 partial match
blocks

Monitoring capacity and taking action to maintain availability directly reduces unchecked resource allocation.

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

Baseline comparison of CPU, memory and bandwidth usage helps surface uncontrolled resource allocations before they cause service degradation.

finds

A.8.29's combined programme of code review, static analysis, dynamic testing and penetration testing reaches CWE-770 through both SOURCE and RUNTIME: missing throttling, unbounded allocation loops and absent connection limits are patterns static analysis and code review surface, and DoS-style stress testing catches them at runtime. The remainder is bounded and nameable — limits that exist but are set too high for the deployment context, race conditions in resource accounting, and design-level decisions about whether a limit belongs at all — which keeps this below the `full` rung A.8.29 reaches on CWE-89.

blocks

Network-level controls in A.8.20 (firewalls with rate limiting, connection filtering, disabling vulnerable protocols) can block some flooding-based resource exhaustion attacks (e.g., TCP/SIP/HTTP floods that exhaust connections or file descriptors), but the underlying application defect — the product allocating resources without limits — remains present and exploitable through single-request vectors (large image bands, oversized MIME parts, large length values) that network controls do not reach.

prevents

A.8.28 mandates secure coding practices — threat modelling, coding standards, peer review, knowledge of common defects — that can catch missing resource limits before code ships, but it is a fallible human practice whose coverage depends on implementer rigour, leaving a nameable remainder that A.8.29 testing reaches more reliably.

prevents

A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-770 is such an ordinary software weakness (missing limits in resource allocation), and the clause's declared ceiling on this verb is `partial`.

finds

A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw. CWE-770 does commonly surface as CVEs (multiple observed examples in third-party libraries, interpreters, and products), so the disclosed minority is findable; the majority of CWE-770 instances live in first-party custom code that never receives a CVE and is outside A.8.8's reach.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.

Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.

Oracle Linux 8 (1 rule, 1 more partial)
  • V-248552 OL 8 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. blocks CWE-770
  • V-248553 OL 8 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. blocks CWE-770
Oracle Linux 9 (1 rule, 1 more partial)
  • V-271710 OL 9 must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. blocks CWE-770
  • V-271709 OL 9 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. blocks CWE-770
RHEL 8 (1 rule)
  • V-230244 RHEL 8 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. blocks CWE-770

References