How severe is CVE-2026-3336?

No CVSS score has been assigned to CVE-2026-3336 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-3336?

Affected package information for CVE-2026-3336 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2026-3336?

No patched version of the affected component has shipped for CVE-2026-3336 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2026-3336 in my code and dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for the affected component, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-3336 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-3336?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-3336 can be triaged on real exposure rather than presence alone.

Is CVE-2026-3336 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-3336 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-3336?

CVE-2026-3336 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 54th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-3336?

CVE-2026-3336 is classified as CWE-295 (CWE-295). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-3336 published, and has it been updated?

CVE-2026-3336 was published on March 2, 2026 and was last updated on August 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2026-3336 — Red Hat

CVE-2026-3336 is a CWE-295 vulnerability. A fix is available — see the affected versions and patch details below.

PKCS7_verify Certificate Chain Validation Bypass in AWS-LC

Also known asGHSA-cfwj-9wp5-wqvp GHSA-vw5v-4f2q-w9xfRUSTSEC-2026-0046

Published

Mar 2, 2026

Updated

Aug 22, 2026

Affected

52 versions

Patched

See advisory

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-3336.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Customers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69.0.

Detection & mitigation playbook

Vulnerability

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for the affected component, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of the affected component has shipped for CVE-2026-3336 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-3336 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2026-3336. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat Trusted Artifact Signer 1.3	`rhtas/tuffer-rhel9:1773307309`	RHSA-2026:5459

Frequently Asked Questions

Improper certificate validation in PKCS7_verify() in AWS-LC allows an unauthenticated user to bypass certificate chain verification when processing PKCS7 objects with multiple signers, except the final signer. Customers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69.0.

O3 Security · Impact-Aware SCA

Is CVE-2026-3336 in your dependencies?

O3 Security finds CVE-2026-3336 across dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works