Repository navigation
Triage image findings despite successful Trivy job #2396
Description
Baseline evidence, not a clean-security claim
The rerun Trivy job114153710332 completed for PR#2392 at head 4510ab1469615d4f6db4d2795c0d44b58f289381. Its report contains 19 Node findings (17 HIGH,2 CRITICAL) and6 Python HIGH findings, despite the successful job conclusion.
Scanner-reported criticals:
GHSA-vcvr-r3jv-pc5j: Next16.3.5; reported fix16.3.6.CVE-2026-90711: proxy-addr2.0.7; reported fix2.0.8.
These are scanner observations. Advisory publication dates, applicability and exploitability are UNKNOWN until primary advisory/package evidence and image dependency ancestry are checked. Do not treat the job's success as zero vulnerabilities or a production security approval.
Next reversible action
- Retrieve the exact scan artifact and official package/advisory evidence; record package paths and runtime/build-only ancestry.
- Deduplicate against dependency PRs and existing fixes before changing locks.
- Stage compatible minimal version repairs as separately reviewed PRs; run build, package/security tests and rescan actual image.
- Explicitly distinguish scanner completion from enforced severity gating; assess existing workflow exit-code configuration and propose changes only after baseline triage.
- Close only after a re-fetched image report proves remediation, or separately reviewed applicability/VEX evidence documents each exception.
Owner: UVAI Loop/Codex. State: queued. No production deployment, paid probe or merge. This issue is an evidence-driven blocking item for claiming a clean image, not a claim of a live compromise.
Activity
linear-code commentedon Oct 10, 2026
GRV-807
github-actions commentedon Oct 10, 2026
👋 Thanks for opening this issue! It has been automatically labeled for triage.
groupthinking commentedon Oct 10, 2026
Partial primary-source triage — October10,2026
Upstream Next advisory, published September22,2026, confirms affected versions
>=16.2.0 <16.3.6, patch16.3.6. Its stated exploit condition is Nodenext/ogrendering attacker-controlled values into SVG content/attributes/styles. Edge rendering and absence of those inputs are exclusions in the advisory. This is a baseline advisory, not a newly released capability alert.The inspected OpenGraphImage route at bd0f437 renders static content and accepts no request inputs. That route does not demonstrate the stated attack condition. This is not a full-repository applicability conclusion or a VEX exception; other imports/routes and image dependency ancestry remain to check.
The new deployment-probe PR's completed Trivy job also reports the same19 Node+6 Python findings. It did not repair these packages. Proxy-addr primary-source/date verification remains UNKNOWN after the first search failed to return an authoritative result. No blanket clean-image claim, package mutation, deployment or merge.
groupthinking commentedon Oct 12, 2026
Current-head remediation evidence (2026-10-12)
PR #2409 now points to
1d9f72d7c40bff34aa43b8107cb817ad01e8efd5. Security Scan run 38258616455/job 114843053097 built and scanned exact imagesha256:3e479db974698dc0bf11eec7fbce12acee901a33fe8179570fe4418a6b2ec34e.Retained artifact 11751896119 (ZIP SHA-256
545f1565a67c41fe5a9d641854e74f28bbb7050aa3247e537ca27d4fcb976459) contains source commit, image identity, and SARIF. Independent parsing found 259 HIGH/CRITICAL occurrences: 251 OS, 4 global npm, and 4 from pip's vendor bundle. This is 15 fewer than the prior exact image.Verified absent in the new image report: Next.js, sharp, proxy-addr, source-map-js, devalue, ip-address, pacote, picomatch, sigstore, jaraco.context, and wheel findings.
Unresolved:
The lowercase
trivyfindings gate failed as intended. No exceptions or license-policy relaxation were added. CI/build, E2E, coverage, CodeQL, and issue-link checks passed, but there are no reviews and full branch protection remains unreadable to the GitHub App. PR remains draft and unmerged. See the updated PR body for package paths, exploit preconditions, and authoritative fix versions.