External risk intelligence

Mozilla CA Root Compromise Allows TLS Impersonation

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-113812

This vulnerability affects a client-side software library (Mozilla::CA for Perl) used for certificate validation by local applications. It is not a service or network-accessible endpoint; rather, it is a component embedded within client software, making public internet exposure of the vulnerable surface itself not applicable.

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been identified in a widely used component for managing trusted digital certificates within Perl applications, potentially allowing attackers to impersonate legitimate TLS servers. This could enable them to intercept sensitive communications if client applications are misconfigured to use the affected certificate store. The primary concern is confirming whether our environment relies on this specific component for certificate validation.

  • A flaw allows certificate impersonation.
  • It impacts trust in secure communications.
  • Confirm relevance and exposure of the component.

Attack Path

How an attacker could exploit the issue

An attacker who can intercept or redirect network traffic could impersonate a trusted TLS server by leveraging a compromised root certificate included in the Mozilla::CA bundle. This allows them to intercept sensitive information and potentially perform man-in-the-middle attacks.

  • No user interaction required.
  • Compromised certificate bundle.
  • Impersonate TLS servers.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an attacker able to intercept or redirect client traffic could impersonate a TLS server by leveraging compromised intermediate certificate keys. This affects clients that rely on the affected CA certificate bundle for trust verification.

  • TLS server impersonation.
  • Intercepted or redirected client traffic.
  • Undermined client trust in secure connections.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and infrastructure teams are likely responsible for managing this vulnerability, as it impacts a client-side library used for certificate validation. The first practical step is to identify where Mozilla::CA is used within your environment, confirm if these clients are business-critical or exposed to untrusted networks, and then locate the accountable owner to plan remediation.

  • Identify accountable application owners.
  • Verify client CA store usage.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Mozilla::CA Perl module?

Mozilla::CA is a Perl software component that provides a collection of Certificate Authority (CA) root certificates. Developers use it to verify the identity of TLS servers when their Perl applications, such as LWP or HTTP::Tiny, need to establish secure, encrypted connections over the internet.

What does CWE-295 mean for CVE-2026-113812?

This CVE involves CWE-295, which is the Improper Certificate Validation weakness class. In this specific case, the software trusts a root certificate bundle containing keys that have been compromised. Because the bundle is faulty, the application may incorrectly validate an attacker's fake server as if it were a legitimate, trusted service.

How does an attacker trigger this vulnerability?

An attacker must be positioned to intercept or redirect the client's network traffic to initiate the attack. If the application is configured to use the affected Mozilla::CA bundle for trust decisions, the attacker can present a forged certificate. Note that if an application is configured to use the operating system's default certificate store instead of this Perl-specific module, it is generally not susceptible to this specific flaw.

Do I need to worry about this if my systems are internal?

Halo Surface Signal notes that this is a client-side library issue, not a network-accessible service. Even for internal systems, the risk remains if those applications communicate over untrusted network segments where traffic can be intercepted. You should evaluate if your internal applications rely on this specific certificate bundle for their secure connections.

What are the first steps to address CVE-2026-113812?

Start by identifying which of your Perl applications utilize the Mozilla::CA module for TLS certificate verification. Once identified, check if those clients are configured to fall back to this bundle or if they use the system's certificate store. For systems using the affected bundle, update the Mozilla::CA library to the latest version and ensure the underlying operating system's certificate stores are fully patched.

References