Enterprise LinuxOperating system · Redhat
CVE-2026-2443
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 flaw was identified in libsoup, a widely used HTTP library in GNOME-based systems. When processing specially crafted HTTP Range headers, the library may improperly validate requested byte ranges. In certain build configurations, this could allow a remote attacker to access portions of server memory beyond the intended response. Exploitation requires a vulnerable configuration and access to a server using the embedded SoupServer component.
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 · moderate confidencelibsoup fails to properly validate HTTP Range header byte ranges in certain build configurations, allowing attackers to read server memory beyond intended response boundaries when targeting SoupServer instances.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise LinuxOperating system
= 6.0= 7.0= 8.0= 9.0= 10.0all versionsCVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Identify installed libsoup versionRun 'rpm -q libsoup' on RHEL systems, or 'pkg-config --modversion libsoup-3.0' / 'dpkg -l liblibsoup-3.0-0' on Debian-based systems. For source builds, check the libsoup.pc file or library binary metadata.Affected if The installed version matches any of the affected RHEL versions (6.0, 7.0, 8.0, 9.0, 10.0) or is any version of Gnome Libsoup and SoupServer is in use.
-
Determine if SoupServer is actively usedSearch running processes for applications that link against libsoup and host HTTP servers. Use 'ldd <binary>' or check application documentation to confirm SoupServer usage. Review application code for 'SoupServer' or 'soup_server_new' function calls.Affected if SoupServer instances are running and serving HTTP responses to network clients.
-
Verify HTTP Range header processing is enabledInspect application or server configuration for HTTP Range request handling. Check if the application code processes client Range headers via soup_message_headers_get_ranges or similar libsoup Range APIs.Affected if The SoupServer application accepts and processes HTTP Range headers from clients.
-
Check build configuration for affected setupsReview the libsoup build configuration if accessible. Look for CMake or Meson build logs, or check if the library was built with specific features enabled. The vulnerability exists in certain build configurations.Affected if libsoup was built with a configuration that fails to validate Range header byte ranges properly.
A system is affected if it runs any version of libsoup with an active SoupServer instance that processes HTTP Range headers from clients.
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.
From vendor dataUpdate libsoup to the patched version and review/verify SoupServer configurations to ensure Range header processing is properly constrained.
Fix this in Enterprise Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2443 — 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-2443 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