# CVE-2026-122192: Guest access to Firecracker process memory after a failed memory discard


- **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-48ww-rqpp-2mgm

## What is CVE-2026-122192?

CVE-2026-122192 is a high-severity vulnerability in AWS firecracker, published on 4 Nov 2026. 

### Official description

Improper handling of a failed memory remap in Firecracker versions 0.23.0 through 1.16.1 might allow a guest user with root privileges to read or modify Firecracker VMM process memory via balloon or virtio-mem discard requests on microVMs restored from a snapshot with the File memory backend, if the host fails to create the replacement mapping.

To remediate this issue, users should upgrade to Firecracker 1.16.2 or 1.17.0 and later.

Weakness: CWE-825 (Expired Pointer Dereference), CWE-390 (Detection of Error Condition Without Action)

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


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

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

## Is CVE-2026-122192 being exploited?

There is no known exploitation of CVE-2026-122192 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122192 is a high-severity vulnerability in AWS firecracker, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-122192 in the wild and no public exploit code.

Affected product: AWS firecracker. 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-122192/ (Markdown: https://insights.sbomify.com/CVE-2026-122192/index.md)
```

## Sources

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

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