Skip to content

[INTERNAL] Update audit allowlist for npm 11 paths #1582

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
matz3 merged 1 commit into from
Sep 8, 2026
Merged

[INTERNAL] Update audit allowlist for npm 11 paths #1582

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 9 additions & 7 deletions audit-ci.jsonc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,14 +2,16 @@
// $schema provides code completion hints to IDEs.
"$schema": "https://github.com/IBM/audit-ci/raw/main/docs/schema.json",
"low": true,
// NOTE: Run "npm ci && npm run audit" with npm 11 or higher. Older npm versions report
// different vulnerability paths, so the allowlist below may not match and the audit will fail.
"allowlist": [
// @ui5/project uses only pacote.packument(), pacote.manifest(), and pacote.extract()
// with verifySignatures/verifyAttestations left at their default false.
// Neither the vulnerable sigstore.verify() path nor the DSSE preAuthEncoding code is
// reachable through our call sites, so neither advisory is exploitable via @ui5/project.
"GHSA-jfc7-64v2-mr8c|@sigstore/sign>@sigstore/core",
"GHSA-jfc7-64v2-mr8c|@sigstore/verify>@sigstore/core",
"GHSA-jfc7-64v2-mr8c|@ui5/cli>@ui5/project>pacote>sigstore>@sigstore/core",
"GHSA-jfc7-64v2-mr8c|@sigstore/core>",
"GHSA-jfc7-64v2-mr8c|@sigstore/verify>@sigstore/core>",
"GHSA-jfc7-64v2-mr8c|@ui5/cli>@ui5/project>pacote>sigstore>@sigstore/sign>@sigstore/core",
// GHSA-w4pp-8pjf-rmxw: ReDoS in pacote's addGitSha() function (pacote < 21.5.1).
// The vulnerable code path is only triggered when resolving git specs (git+https://, github:, etc.).
// @ui5/project passes only npm registry specs (pkgName@version) to packument/manifest/extract,
Expand All @@ -25,9 +27,9 @@
// Confirmed upstream in https://github.com/expressjs/express/pull/7440.
// We cannot bump qs ourselves (transitive via express); the fix is pending an Express 4.x
// release (expressjs/express#7439, #7440; expressjs/body-parser#761 merged but unreleased).
"GHSA-4mjr-xmp4-gh2g|@ui5/cli>@ui5/server>express>qs",
"GHSA-4mjr-xmp4-gh2g|body-parser>qs",
"GHSA-x5fp-wj9c-mxmx|@ui5/cli>@ui5/server>express>qs",
"GHSA-x5fp-wj9c-mxmx|body-parser>qs"
"GHSA-4mjr-xmp4-gh2g|qs>",
"GHSA-4mjr-xmp4-gh2g|@ui5/cli>@ui5/server>express>body-parser>qs",
"GHSA-x5fp-wj9c-mxmx|qs>",
"GHSA-x5fp-wj9c-mxmx|@ui5/cli>@ui5/server>express>body-parser>qs"
]
}
Loading