LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1801: Libsoup: libsoup: http request smuggling via malformed chunk headers

A flaw was found in libsoup, an HTTP client/server library. This HTTP Request Smuggling vulnerability arises from non-RFC-compliant parsing in the soup_filter_input_stream_read_line() logic, where libsoup accepts malformed chunk headers, such as lone line feed (LF) characters instead of the required carriage return and line feed (CRLF). A remote attacker can exploit this without authentication or user interaction by sending specially crafted chunked requests. This allows libsoup to parse and process multiple HTTP requests from a single network message, potentially leading to information disclosure.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1801 is a request-smuggling flaw in libsoup, a library used by some Linux software to handle HTTP. A remote unauthenticated attacker could send malformed chunked HTTP traffic that libsoup parses incorrectly. Business urgency is moderate: exposure depends on whether affected systems use libsoup in HTTP-facing request handling paths.

Executive priority

Treat as a moderate-priority infrastructure library issue. Prioritize asset discovery and vendor patch tracking, especially for internet-facing services using libsoup. No source provided confirms active exploitation, so this is not currently a crisis-level item based on available evidence.

Technical view

libsoup’s soup_filter_input_stream_read_line() accepts malformed chunk headers, including LF-only line endings instead of required CRLF. This non-RFC parsing can cause HTTP request smuggling, where multiple requests are interpreted from one network message. Red Hat lists affected libsoup/libsoup3 packages across RHEL 6, 7, 8, 9, and 10.

Likely exposure

Most relevant exposure is HTTP services, proxies, or applications on affected Red Hat platforms that use libsoup/libsoup3 to parse inbound chunked requests. Systems with libsoup installed but not in a network-facing request path may have lower practical exposure.

Exploitation context

The CVSS data indicates network access, low attack complexity, no privileges, and no user interaction. The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. Impact is described as possible request smuggling with potential information disclosure or limited integrity impact.

Researcher notes

The key issue is parser differential behavior around malformed chunk delimiters, classified as CWE-444. Public data identifies affected Red Hat package families but does not provide complete fixed-version details in the supplied bundle. Avoid assuming every application with libsoup installed is exploitable without confirming request-processing context.

Mitigation direction

  • Check Red Hat and GNOME/libsoup advisories for fixed package availability and update guidance.
  • Inventory RHEL 6 through 10 systems for installed libsoup or libsoup3 packages.
  • Prioritize internet-facing or proxy-adjacent applications that parse inbound HTTP using libsoup.
  • Apply vendor-provided updates when available through approved patch channels.
  • If no fix is available, consider reducing exposure of affected HTTP-facing components.

Validation and detection

  • Identify systems running affected Red Hat Enterprise Linux versions.
  • Check whether libsoup or libsoup3 packages are installed.
  • Map applications that depend on libsoup for HTTP server-side or proxy-like behavior.
  • Review vendor advisories for exact fixed versions and package status.
  • Monitor HTTP logs for malformed chunked requests, without attempting exploit reproduction.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-444: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1801 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-1801Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red HatRed Hat Enterprise Linux 10libsoup3affected
Red HatRed Hat Enterprise Linux 6libsoupaffected
Red HatRed Hat Enterprise Linux 7libsoupaffected
Red HatRed Hat Enterprise Linux 8libsoupaffected
Red HatRed Hat Enterprise Linux 9libsoupaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-444 · source CWE mapping

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.