# CVE-2026-113812: Mozilla::CA versions before 20261020 for Perl provide a CA certificate bundle containing a root linked to compromised intermediates.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-109872, BELL-CVE-2026-113812, DEBIAN-CVE-2026-113812, GHSA-h2xv-9jg2-5v55, MGASA-2026-0536, UBUNTU-CVE-2026-113812, openSUSE-SU-2026:12250-1

## What is CVE-2026-113812?

CVE-2026-113812 is a vulnerability in perl-Mozilla-CA, published on 20 Oct 2026. 

### Official description

Mozilla::CA versions before 20261020 for Perl provide a CA certificate bundle containing a root linked to compromised intermediates.

The bundle includes "emSign ECC Root CA - G3", which provides a trust path for intermediate certificates whose private keys are publicly available.

An attacker able to intercept or redirect client traffic may use these keys to impersonate a TLS server.

LWP, HTTP::Tiny and other clients normally use IO::Socket::SSL, which looks for CA certificates in OpenSSL's default locations before falling back to Mozilla::CA.

Configuration and environment variables can override this selection. Users should check which CA store their client uses. If it uses the system store, check for and install the operating system vendor's updates for this incident.

Weakness: CWE-295 (Improper Certificate Validation)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-Mozilla-CA` | openSUSE:Tumbleweed | All versions | 20261020.0.0-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-113812 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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