Skip to content

[Snyk] Security upgrade @angular/compiler from 6.0.9 to 19.2.17#5151

Open
bogarin wants to merge 1 commit intomasterfrom
snyk-fix-e5953a9558402ba594030a4188c0a782
Open

[Snyk] Security upgrade @angular/compiler from 6.0.9 to 19.2.17#5151
bogarin wants to merge 1 commit intomasterfrom
snyk-fix-e5953a9558402ba594030a4188c0a782

Conversation

@bogarin
Copy link
Copy Markdown
Owner

@bogarin bogarin commented Dec 8, 2025

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • spring-boot-modules/spring-boot-angular/src/main/js/ecommerce/package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Cross-site Scripting (XSS)
SNYK-JS-ANGULARCOMPILER-14157154
  706  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Scripting (XSS)

…ckage.json to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-ANGULARCOMPILER-14157154
Copilot AI review requested due to automatic review settings December 8, 2025 04:17
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR attempts to fix a high-severity XSS vulnerability (SNYK-JS-ANGULARCOMPILER-14157154) by upgrading @angular/compiler from version 6.0.9 to 19.2.17. However, this approach creates a critical compatibility issue by upgrading only one Angular package while leaving all other Angular framework dependencies at version 6.0.3, which will break the application.

Key Changes

  • Upgrades @angular/compiler from ^6.0.3 to ^19.2.17 (a 13-major-version jump)
  • Leaves all other Angular packages at v6.0.3, creating severe version mismatches
  • Does not update supporting dependencies (TypeScript, CLI tools) required for Angular 19

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

"@angular/animations": "^6.0.3",
"@angular/common": "^6.0.3",
"@angular/compiler": "^6.0.3",
"@angular/compiler": "^19.2.17",
Copy link

Copilot AI Dec 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upgrading only @angular/compiler to v19.2.17 while all other Angular packages remain at v6.0.3 will cause severe compatibility issues. All Angular framework packages (@angular/animations, @angular/common, @angular/core, @angular/forms, @angular/http, @angular/platform-browser, @angular/platform-browser-dynamic, @angular/router, and @angular/compiler-cli) must be upgraded together to the same major version.

This 13-major-version jump will also introduce breaking changes that require:

  • Updating TypeScript from ~2.7.2 to at least v4.9.3 (required for Angular 19)
  • Migrating through Angular's update guide for each major version
  • Updating build tooling and CLI packages
  • Reviewing and updating application code for breaking changes

Consider either:

  1. Upgrading all Angular packages together following the Angular Update Guide, or
  2. Finding an alternative mitigation for the XSS vulnerability that doesn't require such a major version jump
Suggested change
"@angular/compiler": "^19.2.17",
"@angular/compiler": "^6.0.3",

Copilot uses AI. Check for mistakes.
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.

3 participants