Stack-based Buffer OverflowWeakness · CWE-121

CVE-2026-1761

HIGH · 8.6 CVSS v3.1 Published 2026-02-02

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

95/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

A flaw was found in libsoup. This stack-based buffer overflow vulnerability occurs during the parsing of multipart HTTP responses due to an incorrect length calculation. A remote attacker can exploit this by sending a specially crafted multipart HTTP response, which can lead to memory corruption. This issue may result in application crashes or arbitrary code execution in applications that process untrusted server responses, and it does not require authentication or user interaction.

Technical summary

dbcve analysis · moderate confidence

A stack-based buffer overflow vulnerability exists in libsoup's multipart HTTP response parsing due to an incorrect length calculation. A remote attacker can exploit this by sending a specially crafted multipart HTTP response, causing memory corruption that may lead to application crashes or arbitrary code execution.

MitigationUpdate libsoup to the patched version that corrects the length calculation in multipart response parsing. Validate and sanitize all incoming HTTP responses before processing multipart data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: High
Availability: Low

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm libsoup is installed

Run 'pkg-config --modversion libsoup-3.0' or 'dpkg -l | grep libsoup' (Debian) or 'rpm -q libsoup' (RHEL) to check if libsoup library is present on the system

Affected if libsoup is not installed on the system
Identify installed libsoup version

Execute 'pkg-config --modversion libsoup-3.0' or check your distribution package manager for the installed libsoup version number

Affected if The installed version has not yet received a patch for CVE-2026-1761 (compare your version to any official advisory release notes)
Determine if application parses multipart HTTP responses

Review application source code or configuration for use of libsoup multipart response handling functions (such as soup_multipart_* APIs or Content-Type: multipart/* handling)

Affected if The application uses libsoup to process multipart HTTP responses from servers
Check if processing untrusted HTTP responses

Audit network-facing application behavior to determine if it makes HTTP requests to untrusted or user-controlled servers that could return malicious multipart responses

Affected if Applications process HTTP responses from untrusted or unauthenticated network sources using libsoup
Review application logs for crashes or anomalies

Search system and application logs (/var/log/syslog, application log files) for unexpected crashes, segfaults, or memory corruption indicators occurring after HTTP response processing

Affected if Crashes or abnormal behavior correlate with HTTP response reception in libsoup-using applications

You are affected if libsoup is installed, you are running an unpatched version, and your application uses libsoup to parse multipart HTTP responses from untrusted network sources.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update libsoup to the patched version that corrects the length calculation in multipart response parsing. Validate and sanitize all incoming HTTP responses before processing multipart data.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing6.0 h
Review / QA3.0 h

16.0 hours of engineering $2,760

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-1761 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1761 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-1761?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 8.6 High

Exploit likelihood EPSS, next 30 days 0.9%

Remediation

A high-priority fix

Have this fixed 16 hrs · Moderate

Typical engagement from $2,760

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-1761 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References