NVD / CVE Program· CNA GitHub_M

CVE-2026-50171: Angular: Denial of Service (DoS) via OOM in Number Formatting (digitsInfo)

Noroxi assessment

Priority: Monitor (action score 32/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: angular angular 22.0.0-rc.2.

Low priority for now. Upgrade to angular angular 22.0.0-rc.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Angular 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.

HighCVSS 8.2 · v4.0—No exploit Fix available

GHSA-p3vc-36g9-x9gr

Published: Jun 22, 2026
Updated: Jul 9, 2026
EPSS: 0.2% · 17th percentile
CWE: CWE-400

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 32 / 40 · 8.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 8.2; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
angular	angular	cpe:2.3:a:angular:angular

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

angular angularup to 18.2.14 inclusive
angular angular19.0.0 and later · before 19.2.23
angular angular20.0.0 and later · before 20.3.22
angular angular21.0.0 and later · before 21.2.15
angular angular22.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

angular angular
- >= 22.0.0-next.0, < 22.0.0-rc.2, >= 21.0.0-next.0, < 21.2.15, >= 20.0.0-next.0, < 20.3.22, >= 19.0.0-next.0, < 19.2.23, <= 18.2.14affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	angular.js	from 0	—
npm	@angular/common	from 19.0.0-next.0 · before 19.2.23	19.2.23
npm	@angular/common	from 20.0.0-next.0 · before 20.3.22	20.3.22
npm	@angular/common	from 21.0.0-next.0 · before 21.2.15	21.2.15
npm	@angular/common	from 22.0.0-next.0 · before 22.0.0-rc.2	22.0.0-rc.2
npm	@angular/common	up to and including 18.2.14	—

Same product

angular: all records

Other highest-scoring records for the same primary product.

CVE-2026-68945Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
35Monitor
CVE-2026-50168Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass
35Monitor
CVE-2026-46417Angular: SSRF via Hostname Hijacking in @angular/platform-server
35Monitor

Published before and after this one in the same product

← EarlierCVE-2026-50169Jun 22, 2026 · Angular Service Worker Policy-Bypass & Credential-Stripping Vulnerabilities
22Monitor
← EarlierCVE-2026-50170Jun 22, 2026 · Angular: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache
32Monitor
Later →CVE-2026-50184Jun 22, 2026 · Angular: Request Credential & Cache Policy Stripping in Angular Service Worker
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
angular angular	22.0.0-rc.2 · description	Vendor (CNA)
npm:@angular/common	19.2.23	Package registry (OSV)
npm:@angular/common	20.3.22	Package registry (OSV)
npm:@angular/common	21.2.15	Package registry (OSV)
npm:@angular/common	22.0.0-rc.2	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-101895114 days apartAngular SSR: Denial of Service (DoS) via Infinite Loop on Malformed DOCTYPE
34Monitor
CVE-2026-542680 days apartAngular: Denial of Service (DoS) via OOM in Date Formatting (formatDate)
32Monitor
CVE-2026-101896114 days apartAngular: Denial of Service via Numeric URL Matrix Parameters in Server-Side Rendering (SSR)
32Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: X

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Endpoint Denial of ServiceT1499

Change log

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/angular/angular/security/advisories/GHSA-p3vc-36g9-x9gr

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records