Skip to main content
Mallory
HighVulnerability

CVE-2026-63076: OpenSSL CMP PBM Verification Invalid Pointer Dereference

Published Aug 25, 2026 · Updated 6 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days17 mentions · peak 5 in a dayToday
CVSS7.5High · v3.1
EPSS1.6%76th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
OpenSSL Software Foundation
IdentifiersCVE-2026-63076CWE-476 · NULL Pointer Dereference

CVE-2026-63076 is an invalid pointer dereference in OpenSSL Certificate Management Protocol (CMP) password-based MAC (PBM) protection verification. The verification code obtains the protectionAlg parameter type and value through X509_ALGOR_get0(), but checks only whether the value pointer is non-NULL before casting it to ASN1_STRING and interpreting it as a PBMParameter. A crafted CMP message containing an unexpected ASN.1 parameter type can therefore trigger an invalid pointer dereference and application crash. Server-side processing is reachable through OSSL_CMP_SRV_process_request(); client-side processing occurs during CMP response validation. The failure occurs before MAC computation, so exploitation does not require knowledge of the PBM shared secret.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote, unauthenticated attackers can crash applications operating as CMP servers that accept PBM-protected messages, causing denial of service. CMP clients can also be crashed when processing responses from malicious or intercepted CMP servers. The vulnerability does not provide memory disclosure, a controlled memory write, or a path to code execution. Exposure depends on explicitly enabled CMP functionality and reachable PBM verification. OpenSSL FIPS modules are unaffected because CMP code resides outside the FIPS module boundary.

Mitigation

If you can’t patch tonight, do this now.

Until patched, disable CMP functionality or PBM-protected CMP message processing where unnecessary. Restrict CMP servers to trusted peers and network segments rather than exposing PBM verification to untrusted networks. Configure CMP clients to use authenticated, trusted servers over protected transport to reduce exposure to malicious or on-path responses. These controls reduce reachability but do not correct the parameter-type validation flaw.

Remediation

Patch, then assume compromise.

Install the vendor-provided OpenSSL security update for the operating system or affected application, including updates to bundled libraries and container images. Distribution-specific fixed packages include Debian trixie OpenSSL 3.5.7-1~deb13u2, Ubuntu 26.04 LTS 3.5.5-1ubuntu3.4, Ubuntu 24.04 LTS 3.0.13-0ubuntu3.15, and Ubuntu 22.04 LTS 3.0.2-0ubuntu1.29; later applicable vendor security updates are also suitable. Restart or redeploy applications after updating so they load the patched library. For statically linked or embedded OpenSSL copies, deploy the corresponding updated application or firmware.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenSSL Software FoundationOpensslapplication
FAQ

Frequently asked questions

Is CVE-2026-63076 exploited in the wild?
As of Nov 11, 2026, Mallory has no reports of CVE-2026-63076 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-63076?
As of Nov 11, 2026, Mallory has found no public exploit for CVE-2026-63076.
Is there a patch for CVE-2026-63076?
Install the vendor-provided OpenSSL security update for the operating system or affected application, including updates to bundled libraries and container images. Distribution-specific fixed packages include Debian trixie OpenSSL 3.5.7-1~deb13u2, Ubuntu 26.04 LTS 3.5.5-1ubuntu3.4, Ubuntu 24.04 LTS 3.0.13-0ubuntu3.15, and Ubuntu 22.04 LTS 3.0.2-0ubuntu1.29; later applicable vendor security updates are also suitable.
What products are affected by CVE-2026-63076?
OpenSSL Software Foundation Openssl.
How severe is CVE-2026-63076?
CVE-2026-63076 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 1.6% (76th percentile) as of Nov 11, 2026.
Activity feed

Recent activity

64 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+31 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity8Community discussion across Reddit, Mastodon, and other social sources.