CVE-2026-3338: PKCS7_verify Signature Validation Bypass in AWS-LC
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.
Security readout for executives and security teams
Plain-English summary
Affected applications may accept tampered PKCS7 signed data as authentic because AWS-LC can incorrectly validate signatures containing Authenticated Attributes. This can undermine decisions that depend on trusted signed content. AWS states that customers using AWS services do not need to act; independently operated applications using AWS-LC should be assessed and upgraded.
Executive priority
Treat this as a high-priority integrity issue for applications using AWS-LC to trust PKCS7 signatures, especially when content arrives from untrusted networks. Inventory immediately and upgrade confirmed deployments promptly. Do not divert remediation resources for AWS-managed services, which AWS identifies as requiring no customer action.
Technical view
AWS-LC PKCS7_verify() contains improper signature validation for PKCS7 objects with Authenticated Attributes. An unauthenticated attacker can bypass verification where an application processes attacker-controlled objects through this path. The issue is CWE-347 with CVSS 4.0 score 8.7, reflecting network reachability, low complexity, no privileges or interaction, and high integrity impact.
Likely exposure
Exposure is limited to applications embedding or linking AWS-LC and passing untrusted PKCS7 objects with Authenticated Attributes to PKCS7_verify(). AWS service customers are unaffected according to AWS. The bundle does not clearly establish the complete vulnerable version range; it names 1.41.0 while also marking its default status unaffected.
Exploitation context
The CVSS assessment supports unauthenticated network exploitation when an exposed application processes attacker-controlled PKCS7 content. The bundle marks this CVE as absent from KEV and provides no cited evidence of active exploitation. Actual reachability depends on application data flows and use of the affected function.
Researcher notes
The core weakness is CWE-347 in Authenticated Attributes handling within PKCS7_verify(). Validate reachability and deployed library provenance before classifying exposure. The supplied version metadata is internally ambiguous, so avoid asserting a vulnerable range beyond vendor-confirmed applicability. No active exploitation is established by the provided evidence.
Mitigation direction
Inventory applications that directly or transitively include AWS-LC.
Upgrade affected application deployments to AWS-LC 1.69.0 as directed by AWS.
Prioritize internet-facing and trust-sensitive PKCS7 processing paths.
Consult the AWS advisory where version applicability remains uncertain.
Validation and detection
Confirm deployed artifacts use AWS-LC 1.69.0.
Identify code paths invoking PKCS7_verify() on externally supplied content.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-347 · source CWE mapping
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.