CVE-2026-7511: PKCS7_verify signer confusion allows forged signatures to be accepted

highCVSS 7.5CVE-2026-7511

CSIRTS triage

Other

What: A signer confusion allows forged signatures to be accepted in PKCS7_verify.
Who is affected: Deployments using PKCS7 verification are affected.
Urgency: Remediation is high urgency due to the potential for serious security breaches.
Action: Update to the patched version of the PKCS7 verification library.

AI-assisted analysis generated from the source advisory — verify against the original.

Details

Source: Microsoft Security Response Center (INTL · vendor-psirt · site)
Severity: high — CVSS 7.5
Published: 2026-06-09
Exploitation: Not in CISA KEV at last sync

Original advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-7511

Exploitation outlook

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Low exploitation riskCVE-2026-75110.17% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 7% of all scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2026-7511	coverage & exploitation status	NVD · CVE.org

Same CVEs, other sources

How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.

highCVE-2026-7511: PKCS7_verify signer confusion allows forged signatures, where the signer associated with a sign…nvd

Recent advisories for PKCS7_verify signer confusion

A cluster of recent advisories against the same product widens the attack surface — attackers routinely chain freshly published CVEs on one product, so review these together.

highCVE-2026-7511: PKCS7_verify signer confusion allows forged signatures, where the signer associated with a sign…nvd · 2026-06-25