Skip to content

UID2-7707: suppress CVE-2026-73650 in .trivyignore #209

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
swibi-ttd merged 1 commit into from
Aug 18, 2026
Merged

UID2-7707: suppress CVE-2026-73650 in .trivyignore #209

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
12 changes: 12 additions & 0 deletions .trivyignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,3 +51,15 @@ CVE-2026-67213 exp:2026-11-11
# path
# See: UID2-7659
GHSA-5p4m-2wfm-xmqj exp:2026-11-11

# CVE-2026-73650 — svgo (HIGH).
# Not exploitable here: svgo appears only in the two scanned react-client-side lockfiles
# (javascript-sdk & google-secure-signals): svgo@3.3.3 (@svgr/plugin-svgo dep), postcss-svgo's
# svgo@2.8.1, and svgo@1.3.2 bundled in react-scripts@5/@svgr/webpack@5.5.0. No src/ file
# imports svgo or calls optimize() (grep in both src trees returned nothing). Dockerfile runs
# `npm run build` (CRA) then `npm start` -> server.js is plain express serving the static
# build; svgo runs only at CRA build time on the app's own trusted SVG assets, never against
# untrusted request input. removeScripts/removeScriptElement plugin is disabled by default and
# not configured.
# See: UID2-7707
CVE-2026-73650 exp:2026-11-18