Skip to content

fix(security): follow-redirects 1.16.2 (nightly red) - #188

Merged
WolfTasks merged 1 commit into
mainfrom
fix/follow-redirects-1.16.2
Oct 31, 2026
Merged

WolfTasks merged 1 commit into
mainfrom
fix/follow-redirects-1.16.2

Conversation

@WolfTasks

Copy link
Copy Markdown
Owner

Summary

The Nightly Security Scan went red on 2026-10-31 with no code changes: a new advisory, CVE-2026-116689 (HIGH), flags follow-redirects 1.16.1, a transitive dependency via axios. Fixed in 1.16.2.

Only the follow-redirects entry in frontend/package-lock.json changes (version, resolved, integrity). The edit is surgical because npm update strips the libc fields. package.json is untouched, since axios's ^1.16.0 range already allows 1.16.2.

Verification (local)

  • Trivy fs scan with the nightly's severity gate: 1 HIGH before, 0 after, exit 0
  • npm ci installs 1.16.2 and leaves the lockfile unchanged
  • audit-gate.mjs passes
  • npm run build passes

Refs #187. The nightly needs a green run after merge before that issue is closed.

🤖 Generated with Claude Code

CVE-2026-116689 (HIGH): the sensitiveHeaders option is dropped for arrays
from another realm, so credential headers can reach a cross-origin redirect
target. Surgical lockfile edit because npm update strips the libc fields.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@WolfTasks
WolfTasks merged commit 10cf301 into main Oct 31, 2026
11 checks passed
@WolfTasks
WolfTasks deleted the fix/follow-redirects-1.16.2 branch October 31, 2026 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant