AngularFramework / library
CVE-2026-50171
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAngular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23, a Denial of Service (DoS) vulnerability exists in the @angular/common package of Angular. The formatNumber function, which is also utilized by DecimalPipe, PercentPipe, and CurrencyPipe, does not properly validate the upper bounds of the digitsInfo parameter. Specifically, the minimum and maximum fraction digits parsed from the digitsInfo string (e.g., 1.2-4) are converted to integers and used without limits. When parsing a maliciously crafted digitsInfo string with excessively large fraction digit values (e.g., 1.200000000-200000000), the internal roundNumber function attempts to pad the digits array to match the requested fraction size. This results in an unbounded loop that repeatedly pushes elements into an array. This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA Denial of Service vulnerability exists in Angular's @angular/common package where the formatNumber function (used by DecimalPipe, PercentPipe, and CurrencyPipe) does not validate upper bounds of the digitsInfo parameter. When parsing a malicious digitsInfo string with excessively large fraction digit values (e.g., 1.200000000-200000000), the internal roundNumber function attempts to pad an array to match the requested fraction size, causing an unbounded loop.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
AngularFramework / library
<= 18.2.14>= 19.0.0, < 19.2.23>= 20.0.0, < 20.3.22>= 21.0.0, < 21.2.15= 22.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Angular versionRun 'npm list @angular/core' or check package.json to identify the installed version of @angular/coreAffected if The version is <= 18.2.14, >= 19.0.0 and < 19.2.23, >= 20.0.0 and < 20.3.22, >= 21.0.0 and < 21.2.15, or exactly 22.0.0
-
Identify pipe usageSearch codebase for imports or usage of DecimalPipe, PercentPipe, or CurrencyPipe from @angular/commonAffected if These pipes are used in the application and the Angular version is vulnerable
-
Check for dynamic digitsInfoSearch code for dynamic construction of digitsInfo strings (e.g., string interpolation, template variables, user input) passed to decimal, percent, or currency pipesAffected if digitsInfo parameter can be influenced by user-controlled data rather than static strings
-
Review template usage patternsExamine component templates (.html files) and code for pipe usage with digitsInfo parameter, looking for patterns like [value]="num | number:'1.' + dynamicFraction"Affected if Templates or code pass dynamic or user-supplied values to the digitsInfo parameter of number-related pipes
You are affected if your Angular version is within the vulnerable ranges AND your application uses DecimalPipe, PercentPipe, or CurrencyPipe with a digitsInfo parameter that can be controlled or influenced by dynamic/user input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped19.2.2320.3.2221.2.15
Update Angular to version 22.0.0-rc.2, 21.2.15, 20.3.22, or 19.2.23 or later to receive the patch that adds proper validation for the digitsInfo parameter bounds.
Upgrade to 19.2.23 (for 19.x), 20.3.22 (for 20.x), 21.2.15 (for 21.x), or 22.0.0-rc.2+ (for 22.x)
- Identify the current Angular version in your project by checking package.json
- If using Angular <= 18.2.14: Upgrade to Angular 19.2.23 or later (preferably latest 19.x LTS)
- If using Angular 19.0.0 - 19.2.22: Upgrade to Angular 19.2.23
- If using Angular 20.0.0 - 20.3.21: Upgrade to Angular 20.3.22
- If using Angular 21.0.0 - 21.2.14: Upgrade to Angular 21.2.15
- If using Angular 22.0.0 - 22.0.0-rc.1: Upgrade to 22.0.0-rc.2 or later
- Run npm install or yarn install to update dependencies
- Rebuild and test the application to ensure no regressions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Angular
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50171 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50171 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data