dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-11460

HIGH · 7.3 CVSS v3.1 Published 2026-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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
A flaw has been found in Boost Serialization up to 1.91. The impacted element is an unknown function. This manipulation causes improper validation of specified type of input. It is possible to initiate the attack remotely. The exploit has been published and may be used. The maintainer was notified on Aug 2025 and a disclosure deadline was set for 90 days. The maintainer acknowledged but postponed indefinitely citing time concerns. No patch is currently available and the disclosure deadline has expired.

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

A high-severity improper input validation vulnerability exists in Boost Serialization library up to version 1.91. The issue affects an unspecified serialization function, allowing malformed input to be processed without proper type validation. This could allow attackers to cause unexpected behavior or potentially achieve code execution through specially crafted serialized data.

MitigationUntil an official patch is released, organizations should isolate Boost Serialization components behind strict input validation layers, apply network segmentation to limit exposure, and audit all code paths that deserialize untrusted data using Boost Serialization.

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
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 Boost Serialization library version
    Run 'dpkg -l | grep boost-serialization' (Debian/Ubuntu), 'rpm -qa | grep boost-serialization' (RHEL/CentOS), or check header file version in /usr/include/boost/version.hpp for BOOST_VERSION macro
    Affected if The installed version is 1.91 or lower, indicating the library contains the unpatched vulnerability
  2. Locate Boost Serialization binaries or linked executables
    Use 'ldd <executable>' on suspected applications or run 'find / -name "*boost*serialization*" 2>/dev/null' to find library files, then check which binaries link against them
    Affected if Any production application links against an unpatched Boost Serialization library version 1.91 or below
  3. Audit code for Boost Serialization usage
    Search source code for '#include <boost/serialization/>' and look for calls to load, deserialize, or unserialize functions on untrusted input streams
    Affected if Code deserializes data from network sources, user uploads, or other untrusted origins using Boost Serialization functions
  4. Inspect serialization input sources
    Review application configuration and network logs to determine if Boost Serialization handles data from external or untrusted sources such as HTTP requests, message queues, or file uploads
    Affected if The application deserializes data originating from outside the trusted execution boundary
  5. Check for type-aware deserialization safeguards
    Review code using BOOST_CLASS_EXPORT, BOOST_CLASS_TYPE_TRACKING, or custom archive handlers to verify if type validation is explicitly enforced before deserialization
    Affected if The application relies solely on Boost Serialization's default behavior without additional input validation layers

You are affected if your environment uses Boost Serialization library version 1.91 or lower and deserializes any untrusted or externally-sourced data using this library.

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

Until an official patch is released, organizations should isolate Boost Serialization components behind strict input validation layers, apply network segmentation to limit exposure, and audit all code paths that deserialize untrusted data using Boost Serialization.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11460 — 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-11460 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