Skip to content

fix(deps): release 10 Dependabot security patches to master - #105

Merged
GaetanOff merged 2 commits into
masterfrom
develop
Aug 4, 2026
Merged

fix(deps): release 10 Dependabot security patches to master#105
GaetanOff merged 2 commits into
masterfrom
develop

Conversation

@GaetanOff

Copy link
Copy Markdown
Owner

Summary

Promotes the security fixes from develop to master. This is the release step that actually closes the 10 Dependabot alerts — they only auto-resolve on the default branch (master).

Contains a single commit: 3f24e2a (merged via #104).

Alerts closed by this merge

Alert Severity Package Advisory
#249 high @angular/core GHSA-jj27-h5hq-8x99 — i18n XSS via event-handler attributes
#248 high @angular/compiler GHSA-jj27-h5hq-8x99 — i18n XSS via event-handler attributes
#247 high @angular/common GHSA-jhpw-976m-542j — HttpTransferCache cache-key ambiguity
#253 high undici GHSA-4cwx-7wf7-3272 — disclosure + parse-time crash
#256 medium undici GHSA-m8rv-5g2x-5cg5 — CRLF injection
#255 medium undici GHSA-v3r7-h72x-cjcm — cookie attribute injection
#254 medium undici GHSA-jr45-8vmc-qm54 — disclosure via Cache-Control whitespace
#252 medium undici GHSA-8xcm-r25x-g524 — response desync via retry interceptor
#251 medium ip-address GHSA-4xrf-jv44-h6hh — SSRF check bypass via CIDR suffix
#250 medium ip-address GHSA-22jq-vg5j-6vgg — IPv4-mapped/NAT64 misclassification

Scope

Two files, no application source:

  • package.json@angular/*^21.2.19, overrides.undici^7.29.0, overrides.ip-address^10.2.2
  • package-lock.json — regenerated (npm cannot do the Angular lockstep peer upgrade incrementally); all incidental bumps stay inside ranges already declared in package.json

master had no commits absent from develop at the time of opening, so this is a clean fast-forward with no divergence to reconcile.

Verification

Already validated on #104, CI green:

  • npm audit0 vulnerabilities
  • npm ci → succeeds, lockfile in sync
  • npm run build (production) → succeeds
  • npm run test:ci39/39 passing

Note

Dependabot PR #103 (@angular/common 21.2.17 → 22.1.0) targets master and overlaps with this one. This PR fixes the same advisory by staying on the 21.2.x patch line instead of taking a major upgrade, so #103 should be closable as superseded once this merges — worth confirming rather than merging both.

🤖 Generated with Claude Code

GaetanOff and others added 2 commits August 4, 2026 14:48
Resolves all 10 open Dependabot alerts on the repository.

Angular 21.2.17 -> 21.2.19 (alerts #247, #248, #249)
- GHSA-jj27-h5hq-8x99 (high): i18n XSS via event-handler attributes
  (@angular/core, @angular/compiler)
- GHSA-jhpw-976m-542j (high): cache-key ambiguity in HttpTransferCache
  leading to cross-request response reuse and state poisoning
  (@angular/common)
The whole @angular/* set moves together because these packages carry
exact peer ranges on one another.

undici -> 7.29.0 override floor (alerts #252-#256)
- GHSA-4cwx-7wf7-3272 (high): cross-user info disclosure and parse-time
  crash via degenerate private cache directives
- GHSA-m8rv-5g2x-5cg5: CRLF injection via blob-like body type
- GHSA-v3r7-h72x-cjcm: cookie attribute injection
- GHSA-jr45-8vmc-qm54: disclosure via whitespace in Cache-Control
- GHSA-8xcm-r25x-g524: response desync via retry interceptor

ip-address -> 10.2.2 override floor, resolves to 10.4.0 (alerts #250, #251)
- GHSA-4xrf-jv44-h6hh: CIDR suffix suppresses special-use
  classification, bypassing SSRF and trust-boundary checks
- GHSA-22jq-vg5j-6vgg: misclassification of IPv4-mapped/NAT64 IPv6

The lockfile was regenerated because npm cannot perform the Angular
lockstep peer upgrade incrementally; the incidental transitive bumps all
sit inside the semver ranges already declared in package.json.

Verified: npm audit reports 0 vulnerabilities, npm ci succeeds,
production build succeeds, 39/39 unit tests pass.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…ip-address

fix(deps): patch 10 Dependabot alerts (Angular XSS, undici, ip-address)
@GaetanOff
GaetanOff merged commit 1c06237 into master Aug 4, 2026
6 checks passed
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