CVE-2026-15712
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA heap buffer over-read vulnerability was discovered in libsoup's (versions: libsoup 3.0 to 3.7.0) HTTP/2 connection tracking framework. When the library processes an HTTP/2 GOAWAY frame, it improperly handles the "Additional Debug Data" payload by assuming the data stream is a safely NUL-terminated C-string. Because the parser lacks strict length-boundary verification before reading this data, a remote, unauthenticated attacker can intentionally send a malformed GOAWAY frame missing the appropriate null delimiter. This causes the library to read past the end of the allocated buffer, triggering an application crash that results in a denial of service (DoS), or potentially exposing fragments of memory contents.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencelibsoup 3.0 to 3.7.0 contains a heap buffer over-read in its HTTP/2 GOAWAY frame handling. The parser incorrectly assumes the Additional Debug Data field is a NUL-terminated C-string without verifying length boundaries, causing it to read past the allocated buffer when a malformed frame lacks a null delimiter.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if libsoup3 is installedRun `pkg-config --modversion libsoup-3.0` or `dpkg -l | grep libsoup` on Debian-based systems, or `rpm -q libsoup3` on RHEL-based systemsAffected if libsoup3 package is found with a version between 3.0 and 3.7.0 inclusive
-
Verify libsoup library file versionRun `strings /usr/lib/x86_64-linux-gnu/libsoup-3.0.so* | grep '^3\.` or check the soname with `ldconfig -p | grep libsoup-3.0`Affected if The library file shows version 3.0.x through 3.7.0
-
Confirm HTTP/2 is enabled in the applicationReview application configuration or code that uses libsoup to verify HTTP/2 support is not explicitly disabled (libsoup enables HTTP/2 by default when available)Affected if HTTP/2 protocol support is active in the libsoup client or server implementation
You are affected if libsoup version 3.0 through 3.7.0 is installed and HTTP/2 is enabled, as the vulnerable GOAWAY frame parser will process incoming frames.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade libsoup to version 3.7.1 or later where the boundary check has been implemented. As an interim measure, network-level filtering can block malformed HTTP/2 GOAWAY frames.
libsoup 3.7.1 or later
- 1. Identify the current libsoup version in use by checking your project's dependency files (e.g., meson.build, package.json, or system package manager)
- 2. If using a distribution package (e.g., from Debian, Ubuntu, Fedora), check for available security updates via 'apt list --upgradable' or 'dnf check-update'
- 3. For source-based builds, obtain libsoup version 3.7.1 or later from the official GNOME GitLab repository: https://gitlab.gnome.org/GNOME/libsoup/-/releases
- 4. Rebuild and redeploy the application with the updated libsoup library
- 5. Verify the fix by confirming the new libsoup version is loaded (e.g., via 'pkg-config --modversion libsoup-3.0' or runtime inspection)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15712 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data