Gst-plugins-base: gst-plugins-base: missing bounds checks in rtcp sdes packet parsing
Affects gst-plugins-base versions earlier than 1.28.4 when RTCP packets arrive during an active media session. Fixed in 1.28.4.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.28.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.28.4.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 38/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
A flaw in the RTCP SDES packet parser of GStreamer's gst-plugins-base lets a remote sender reach the affected media session without logging in and without any user action. A malformed SDES entry can make the receiver read past the end of the packet buffer, which may crash the application or expose a limited amount of process memory.
Read the original description
A flaw was found in GStreamer's gst-plugins-base RTCP SDES packet parser. A remote sender able to reach an active media session can supply a malformed SDES entry whose declared length exceeds the received packet. Missing bounds validation can cause the receiver to read beyond the packet buffer, potentially crashing the application or exposing a limited amount of process memory.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Shipped in major Linux distributions
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 83 if added to CISA KEV
- Would score about 78 if CISA's SSVC rates exploitation active
- Would score about 43 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.28.4.
Workaround: Disable the affected RTP session handling elements if RTP/RTCP is not needed, or restrict the negotiated RTCP port to trusted peers with network controls.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-125712 (Gst-plugins-base: gst-plugins-base: missing bounds checks in rtcp sdes packet parsing), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-125712 (entry last updated 2026-11-10): Affected: - Red Hat Red Hat Enterprise Linux 10: version range not reported - Red Hat Red Hat Enterprise Linux 6: version range not reported - Red Hat Red Hat Enterprise Linux 7: version range not reported - Red Hat Red Hat Enterprise Linux 7: version range not reported - Red Hat Red Hat Enterprise Linux 8: version range not reported - Red Hat Red Hat Enterprise Linux 9: version range not reported Fixed versions: 1.28.4. Conditions (all must be true for the bug to be hit): - gst-plugins-base version earlier than 1.28.4 (source: https://gstreamer.freedesktop.org/security/sa-2026-0030.html) - RTCP packets arrive during an active media session (source: https://access.redhat.com/security/cve/cve-2026-125712) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, no user action. Workaround: Disable the affected RTP session handling elements if RTP/RTCP is not needed, or restrict the negotiated RTCP port to trusted peers with network controls. (source: https://gstreamer.freedesktop.org/security/sa-2026-0030.html) CISA KEV: CVE-2026-125712 is not listed as of cve.now's last read. This KEV status is for CVE-2026-125712 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://bugzilla.redhat.com/show_bug.cgi?id=2569130 - https://access.redhat.com/security/cve/CVE-2026-125712 - https://gstreamer.freedesktop.org/security/sa-2026-0030.html - https://access.redhat.com/security/cve/cve-2026-125712 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-125712 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125712.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- gstreamer1-plugins-base
Version range not reported
- gstreamer-plugins-base
Version range not reported
- gstreamer1-plugins-base
Version range not reported
- gstreamer-plugins-base
Version range not reported
- gstreamer1-plugins-base
Version range not reported
- gstreamer1-plugins-base
Version range not reported
Evidence 5
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Write-ups · 1
Establishes: Technical detail and context.
- Report
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125712
Is CVE-2026-125712 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The RTCP SDES packet parser in gst-plugins-base does not check bounds properly on invalid SDES data, so it can read memory outside the intended buffer. This can crash the application or expose process memory.Source: gstreamer.freedesktop.org, access.redhat.com
Am I affected, and how do I check?
Versions of gst-plugins-base earlier than 1.28.4 are affected, in setups where RTCP packets arrive during an active media session. Check the installed gst-plugins-base version to see which release is in use.Source: gstreamer.freedesktop.org, access.redhat.com
How do I fix CVE-2026-125712?
Upgrade gst-plugins-base to version 1.28.4 or later, which contains the fix.Source: gstreamer.freedesktop.org, access.redhat.com