DirectorySecurity AdvisoriesPricing
Sign in
Security Advisories

CVE-2026-4923

NVD

https://nvd.nist.gov/vuln/detail/CVE-2026-4923

Severity

5.9

Medium

CVSS V3

Eliminate CVEs with Chainguard hardened images

Build, ship, and run secure software with minimal, hardened container images — rebuilt from source daily and guarded under our industry-leading remediation SLA.

Start for free

Summary

path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards

Description

Impact:

When using multiple wildcards, combined with at least one parameter, a regular expression can be generated that is vulnerable to ReDoS. This backtracking vulnerability requires the second wildcard to be somewhere other than the end of the path.

Unsafe examples:

/*foo-*bar-:baz /*a-:b-*c-:d /x/*a-:b/*c/y

Safe examples:

/*foo-:bar /*foo-:bar-*baz

Patches:

Upgrade to version 8.4.0.

Workarounds:

If you are using multiple wildcard parameters, you can check the regex output with a tool such as https://makenowjust-labs.github.io/recheck/playground/ to confirm whether a path is vulnerable.

References

  • https://nvd.nist.gov/vuln/detail/CVE-2026-4923
  • https://github.com/advisories/GHSA-27v5-c462-wpq7
  • https://cna.openjsf.org/security-advisories.html
  • https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/4xxx/CVE-2026-4923.json

Affected packages

The trusted source for open source

Talk to an expert
PrivacyTerms

Product

Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing

Solutions

FedRAMPPCI DSSCMMC 2.0SOC 2Golden ImagesCVE RemediationPublic SectorStartups

Customers

Customer StoriesChainguard Reviews

Resources

Events & WebinarsSupply Chain Security 101Chainguard CoursesDocumentationTrust CenterChainguard Slack Community

Company

About UsBlogOpen Source LeadershipPartnersNewsroomCareersLegal
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.