dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2026-1788

MEDIUM · 6.6 CVSS v4.0 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
: Out-of-bounds Write vulnerability in Xquic Project Xquic Server xquic on Linux (QUIC protocol implementation, packet processing module modules) allows : Buffer Manipulation.This issue affects Xquic Server: through 1.8.3.

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 confidence

Out-of-bounds write vulnerability in the packet processing module of Xquic Server (versions through 1.8.3) on Linux allows buffer manipulation via specially crafted QUIC packets. This is a memory corruption issue in the QUIC protocol implementation that could lead to crashes or potentially code execution.

MitigationApply vendor patches when available; until then, restrict network exposure of Xquic Server and implement input validation/fuzzing on packet processing paths to detect malformed packets.

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
Low
Privileges
None
Authentication
Y
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:X/RE:M/U:Amber

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 checks

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

  1. Identify Xquic Server installation and version
    Run 'xquic-server -v' or 'xquic-server --version' to obtain the installed version. If not available, check the package manager: 'dpkg -l | grep xquic' or 'rpm -qa | grep xquic' on Linux systems.
    Affected if Version is 1.8.3 or earlier (the vulnerability affects versions through 1.8.3)
  2. Confirm Xquic Server process is running
    Check running processes with 'ps aux | grep xquic' or 'pgrep -a xquic' to determine if the server is currently active.
    Affected if The Xquic Server process is actively running on the system
  3. Verify network exposure of the QUIC service
    Check which ports the Xquic Server is listening on with 'netstat -tlnp | grep xquic' or 'ss -tlnp | grep xquic'. Determine if these ports are bound to externally accessible network interfaces (0.0.0.0 or ::) rather than localhost (127.0.0.1).
    Affected if The QUIC service is bound to a public or routable network interface and accessible from external sources
  4. Check if packet processing module is enabled
    Review Xquic Server configuration files (typically in /etc/xquic/ or /usr/local/etc/xquic/) for active listener configurations that enable QUIC packet processing. Look for 'listen' or 'quic' directives in the config.
    Affected if QUIC packet processing is enabled and the server is configured to accept incoming QUIC connections

If Xquic Server version 1.8.3 or earlier is running with the packet processing module enabled and exposed to the network, the environment is affected by CVE-2026-1788.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches when available; until then, restrict network exposure of Xquic Server and implement input validation/fuzzing on packet processing paths to detect malformed packets.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1788 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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