CVE-2026-3338

HIGHPre-NVD 7.57.5
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Improper signature validation in PKCS7_verify() in AWS-LC allows an unauthenticated user to bypass signature verification when processing PKCS7 objects with Authenticated Attributes.

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

CVSS v3
7.5
EG Score
7.5(low)
EPSS
51.4%
KEV
Not listed

Published

March 2, 2026

Last Modified

June 30, 2026

Advisory Details (7)

Auto-updated Jul 7, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, redhat.
redhat Patch Available

Affected: Red Hat Enterprise Linux 10",

https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-3338.json
redhat Patch Available

2444025 – (CVE-2026-3338) CVE-2026-3338 aws-lc: AWS-LC: Signature bypass due to improper validation in PKCS7_verify()

https://bugzilla.redhat.com/show_bug.cgi?id=2444025
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-3338
github Patch Available🟡 PoC Available

PKCS7_verify Signature Validation Bypass in AWS-LC · Advisory · aws/aws-lc · GitHub

https://github.com/aws/aws-lc/security/advisories/GHSA-jchq-39cv-q4wj
github_release Patch Available

v1.69.0

Patch available: aws/aws-lc v1.69.0

https://github.com/aws/aws-lc/releases/tag/v1.69.0
generic

Issue with AWS-LC: an open-source, general-purpose cryptographic library

https://aws.amazon.com/security/security-bulletins/2026-005-AWS/

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhtas/tuftool-rhel9:17733073092026-03-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
aws-lc-sys0.38.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 04:35 UTCEG score recompute
  10. 2026-06-30 04:35 UTCVendor advisory
  11. 2026-06-30 04:31 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-3338?
CVE-2026-3338 is a high vulnerability published on March 2, 2026. Improper signature validation in PKCS7_verify() in AWS-LC allows an unauthenticated user to bypass signature verification when processing PKCS7 objects with Authenticated Attributes. Customers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version…
When was CVE-2026-3338 disclosed?
CVE-2026-3338 was first published in the National Vulnerability Database on March 2, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3338 actively exploited?
CVE-2026-3338 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 51.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-3338?
CVE-2026-3338 has a CVSS v3 base score of 7.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-3338?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3338, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-3338

Explore →

Is Your Infrastructure Affected by CVE-2026-3338?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.