Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7

AWS-LC has PKCS7_verify Certificate Chain Validation Bypass

GHSA-vw5v-4f2q-w9xf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (aws-lc-sys 0.38.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io aws-lc-sys

    Affected
    >= 0.24.0, < 0.38.0
    Fixed in
    0.38.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary AWS-LC is an open-source, general-purpose cryptographic library. Impact Improper certificate validation in PKCS7verify() 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. aws-lc-sys contains code from AWS-LC. Applications using aws-lc-sys should upgrade to the most recent release of aws-lc-sys. Impacted versions: aws-lc-sys versions: = 0.24.0, < 0.38.0 Patches The patch is included in v0.38.0 Workarounds There is no workaround. Applications using aws-lc-sys should upgrade to the most recent release of aws-lc-sys. Resources If there are any questions or comments about this advisory, contact [AWS/Amazon] Security via the vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. Acknowledgement AWS-LC would like to thank Joshua Rogers…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-vw5v-4f2q-w9xf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-vw5v-4f2q-w9xf

Advisory: AWS-LC has PKCS7_verify Certificate Chain Validation Bypass
IDs: GHSA-vw5v-4f2q-w9xf
Record: https://patchnext.com/advisories/ghsa-vw5v-4f2q-w9xf (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: aws-lc-sys 0.38.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io aws-lc-sys: affected >= 0.24.0, < 0.38.0; fixed in 0.38.0

## Suggested inspection (read-only)
- crates.io aws-lc-sys: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on aws-lc-sys.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vw5v-4f2q-w9xf (GitHub-reviewed advisory GHSA-vw5v-4f2q-w9xf lists affected ranges: crates.io aws-lc-sys >=0.24.0 <0.38.0)

Commands are suggestions: review each one before running it.

Loading voting…