VulnerabilityPublished 6 Aug 2026Updated 23 Sep 2026

CVE-2026-18649: Unthrottled Resource Allocation

Source GCVE Database

Compare

Authoritative record:CVE-2026-18649· High 7.5

Not known to be exploited · CVSS 7.5 High : patch Red Hat Enterprise Linux 10 soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-wr93-5xph-995g

What to do

Patches and advisories

Affected software

Product	Affected	Fixed in
Red Hat Enterprise Linux 10gstreamer1-plugins-good	Affected–	Fixed in–
Red Hat Enterprise Linux 10.0 Extended Update Supportgstreamer1-plugins-good	Affected–	Fixed in–
Red Hat Enterprise Linux 7 Extended Lifecycle Supportgstreamer1-plugins-good	Affected–	Fixed in–
Red Hat Enterprise Linux 8gstreamer1-plugins-good	Affected–	Fixed in–
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Supportgstreamer1-plugins-good	Affected–	Fixed in–
Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-Ongstreamer1-plugins-good	Affected–	Fixed in–

AI-suggested

Meanwhile, mitigations include: (1) Use SRTP or DTLS-SRTP to provide per-packet authentication and reject unauthenticated RTP fragments before they reach the vulnerable depayloaders. (2) Apply network-level restrictions via firewall rules to allow RTP traffic only from trusted sources. (3) Disable the RTP plugin at build time using the meson option "-Drtp=disabled" to remove the vulnerable elements entirely. (4) Prevent the vulnerable depayloaders from being auto-plugged at runtime by setting GST_PLUGIN_FEATURE_RANK=rtph264depay:0,rtph265depay:0, though explicit pipeline construction remains possible.

Description

A vulnerability in the GStreamer gst-plugins-good package affects the rtph264depay and rtph265depay RTP depayloader elements. These elements do not enforce a maximum size limit on the reassembly buffer during fragmented RTP packet processing. An unauthenticated remote attacker can exploit this by sending a continuous stream of RTP fragments without an end-of-fragment marker, causing unbounded memory growth and denial of service via process termination. The risk is significant when processing unauthenticated RTP streams, but mitigations such as using SRTP or DTLS-SRTP, network restrictions, or disabling the RTP plugin reduce exposure.

Impact

The vulnerability allows a remote, unauthenticated attacker to cause a denial of service by exhausting process memory through unbounded growth of the RTP reassembly buffer. This leads to process termination and service disruption. There is no impact on confidentiality or integrity. The attack surface is limited to deployments processing unauthenticated RTP streams without SRTP or DTLS-SRTP protection. Local playback and authenticated RTP streams are not affected.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Patches and advisories

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 15:58 UTC

Public exploits and detectionGitHub proofs of concept

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats