Critical Security Flaw in Angular.js: Untrusted Input Serialization Vulnerability

angular.js Updated 11 Sep 2026

Summary

10/09/2026
N/A
No i
Unrated
Not published

DEBIAN-CVE-2026-88060: Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Affects angular.js versions 1.8.3-1 – 1.8.3-3. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Angular.js is a widely-used development platform for building mobile and desktop web applications using TypeScript, JavaScript, and other languages. It provides a robust framework for creating dynamic web applications, with features like two-way data binding, dependency injection, and modular architecture. However, prior to versions 20.3.30, 21.2.22, and 22.1.4, Angular.js had a significant vulnerability in its server-side rendering (SSR) capabilities, which could lead to severe security risks.

Vulnerability Detail

The vulnerability arises from Angular's server-side rendering (SSR) mechanism in the @angular/platform-server package, which improperly serializes untrusted input within template content. This issue affects fallback raw-content elements such as noscript, iframe, noembed, and noframes. The Domino serializer's traversal of fallbackRawContentTags fails to escape matching closing tags in various nodes, allowing unescaped closing tags to be interpreted as active DOM elements. This can lead to arbitrary JavaScript execution when HTML5 RAWTEXT browser parsing encounters these unescaped tags, posing a significant security threat.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, avoid using untrusted input in template content and ensure that any dynamic content is properly sanitized before rendering. Additionally, consider using strict schemas like CUSTOM_ELEMENTS_SCHEMA or NO_ERRORS_SCHEMA to mitigate risks.

Conclusion

The Angular.js vulnerability CVE-2026-88060 poses a serious risk due to improper handling of untrusted input in server-side rendering. It is crucial to update to the patched versions to safeguard your applications against potential exploitation. Implementing best practices for input handling can also help mitigate risks.

See every vulnerability recorded for angular.js →

Share this vulnerability

FAQ

The vulnerability allows for arbitrary JavaScript execution due to improper serialization of untrusted input in Angular's server-side rendering.

Versions prior to 20.3.30, 21.2.22, and 22.1.4 are affected by this vulnerability.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Exploitation of this vulnerability can lead to arbitrary code execution, which may compromise the security of the application and its users.

Yes, you can implement strict input validation and sanitization, and avoid using untrusted input in your templates as a temporary measure.

Related vulnerabilities

Recent vulnerabilities recorded for angular.js.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback