# CVE-2026-11460: Boost Serialization improper validation of specified type of input

> Remote attackers can exploit improper input validation in Boost Serialization to potentially execute code or cause denial of service.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-25jx-vqmc-84rq

## What is CVE-2026-11460?

CVE-2026-11460 is a medium-severity unsafe deserialization vulnerability in Boost Serialization, published on 7 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation), CWE-1287 (Improper Validation of Specified Type of Input)

## Which versions are affected by CVE-2026-11460?


## How do I fix CVE-2026-11460?

No fix has been published for CVE-2026-11460 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11460 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11460 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11460 and fix it if it is affected.

What it is: CVE-2026-11460 is a medium-severity unsafe deserialization vulnerability in Boost Serialization, published on 7 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11460 exists.

Affected product: Boost Serialization. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-11460/ (Markdown: https://insights.sbomify.com/CVE-2026-11460/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11460
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11460
- OSV: https://osv.dev/vulnerability/CVE-2026-11460

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-11460/
Summaries are generated and may contain mistakes; the official description above is the record.