# CVE-2026-113470: Cryptographic issue in the Security Block-lists, Allow-lists, and other State component


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-113470, GHSA-vr39-qqr3-x9v4, MGASA-2026-0540, OESA-2026-4651, OESA-2026-4652, UBUNTU-CVE-2026-113470, openSUSE-SU-2026:12211-1, openSUSE-SU-2026:22159-1

## What is CVE-2026-113470?

CVE-2026-113470 is a medium-severity vulnerability in Mozilla Firefox, published on 20 Oct 2026. 

### Official description

Cryptographic issue in the Security Block-lists, Allow-lists, and other State component. This vulnerability was fixed in Firefox 158.0.1, Firefox ESR 153.5.1, Firefox ESR 115.43.1, Thunderbird 158.0.1, Thunderbird 153.5.1, and Firefox 158.0.2.

Weakness: CWE-295 (Improper Certificate Validation)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `MozillaFirefox` | openSUSE:Leap 16.0 | All versions | 153.5.1-160000.1.1 |
| `mozilla-nss` | openSUSE:Leap 16.0 | All versions | 3.125-160000.3.1 |
| `firefox-esr` | openSUSE:Tumbleweed | All versions | 153.5.1-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-113470 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113470 is a medium-severity vulnerability in Mozilla Firefox, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113470 in the wild and no public exploit code.

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

## Sources

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

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