CVE-2026-11998

HIGHPre-NVD 7.67.6—
EchelonGraph scoreMEDIUM confidence

Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A flaw in AngularJS' Strict Contextual Escaping (SCE) logic allows bypassing certain SCE policies for resource URLs and can lead to arbitrary JavaScript execution within the context of the victim's browser session.

SCE's purpose is to ensure that only trusted or safe values are used in certain security-sensitive contexts, such as resource URLs, including URLs that define executable JavaScript scripts, '' documents, route templates, etc. A flaw in the logic that tries to match entire URLs against regular expression matchers can result in partial matches for certain types of regular expressions, effectively bypassing the policies and allowing the use of unsafe values as resource URLs.

This issue affects AngularJS versions greater than or equal to 1.2.0-rc.3.

Note: The AngularJS project was already End-of-Life when this CVE was published and will not receive any updates to address this issue. For more information see the  End-of-Life announcement https://docs.angularjs.org/misc/version-support-status .

CVSS v3
7.6
EG Score
7.6(medium)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity76% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Patch available.
generic Patch Available🟡 PoC Available

Vulnerability Directory | CVE-2026-11998 | AngularJS

https://www.herodevs.com/vulnerability-directory/cve-2026-11998?nes-for-angularjs
generic Patch Available🟡 PoC Available

Vulnerability Directory | CVE-2026-11998 | AngularJS

https://www.herodevs.com/vulnerability-directory/cve-2026-11998

Vendor Advisories for CVE-2026-11998(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
npmangular—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
angular.js1.8.2-2, 1.8.3-1, 1.8.3-2, 1.8.3-3——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
angular.js1.8.3-1, 1.8.3-1+deb12u1, 1.8.3-1+deb12u1~deb11u1, 1.8.3-2, 1.8.3-3——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
angular.js1.8.3-3——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
angular.js1.8.3-3——
npm(1)
PackageVulnerable rangeFixed inDependents
angular———

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 115× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 200 total refreshes for this CVE.

  1. 2026-08-25 13:48 UTCEPSS rescore
  2. 2026-08-25 03:02 UTCEG score recompute
  3. 2026-08-25 03:02 UTCGHSA enrichment
  4. 2026-08-24 14:17 UTCEG score recompute
  5. 2026-08-24 14:17 UTCGHSA enrichment
  6. 2026-08-24 01:27 UTCGHSA enrichment
  7. 2026-08-23 12:43 UTCEG score recompute
  8. 2026-08-23 12:43 UTCGHSA enrichment
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 23:59 UTCGHSA enrichment
  11. 2026-08-22 11:15 UTCEG score recompute
  12. 2026-08-22 11:15 UTCGHSA enrichment
  13. 2026-08-21 23:48 UTCEPSS rescore
  14. 2026-08-21 21:27 UTCGHSA enrichment
  15. 2026-08-21 08:42 UTCEG score recompute
  16. 2026-08-21 08:42 UTCGHSA enrichment
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 19:58 UTCGHSA enrichment
  19. 2026-08-20 07:14 UTCEG score recompute
  20. 2026-08-20 07:14 UTCGHSA enrichment
  21. 2026-08-19 17:03 UTCEPSS rescore
  22. 2026-08-19 14:50 UTCGHSA enrichment
  23. 2026-08-19 01:41 UTCEG score recompute
  24. 2026-08-19 01:41 UTCGHSA enrichment
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 06:11 UTCGHSA enrichment
  2. 2026-08-16 17:06 UTCEG score recompute
  3. 2026-08-16 17:06 UTCGHSA enrichment
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 04:22 UTCEG score recompute
  6. 2026-08-16 04:22 UTCGHSA enrichment
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 15:38 UTCGHSA enrichment
  9. 2026-08-15 02:54 UTCEG score recompute
  10. 2026-08-15 02:54 UTCGHSA enrichment
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 14:09 UTCGHSA enrichment
  13. 2026-08-14 01:25 UTCEG score recompute
  14. 2026-08-14 01:25 UTCGHSA enrichment
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-13 12:41 UTCGHSA enrichment
  17. 2026-08-12 23:57 UTCEG score recompute
  18. 2026-08-12 23:57 UTCGHSA enrichment
  19. 2026-08-12 13:50 UTCEPSS rescore
  20. 2026-08-12 11:13 UTCGHSA enrichment
  21. 2026-08-11 22:28 UTCEG score recompute
  22. 2026-08-11 22:28 UTCGHSA enrichment
  23. 2026-08-11 13:42 UTCEPSS rescore
  24. 2026-08-11 09:45 UTCEG score recompute
  25. 2026-08-11 09:45 UTCGHSA enrichment
  26. 2026-08-10 23:59 UTCEPSS rescore
  27. 2026-08-10 21:00 UTCGHSA enrichment
  28. 2026-08-10 08:16 UTCGHSA enrichment
  29. 2026-08-09 19:32 UTCEG score recompute
  30. 2026-08-09 19:32 UTCGHSA enrichment
  31. 2026-08-09 13:46 UTCEPSS rescore
  32. 2026-08-09 06:48 UTCGHSA enrichment
  33. 2026-08-08 18:04 UTCEG score recompute
  34. 2026-08-08 18:04 UTCGHSA enrichment
  35. 2026-08-08 16:37 UTCEPSS rescore
  36. 2026-08-08 05:19 UTCGHSA enrichment
  37. 2026-08-07 16:35 UTCEG score recompute
  38. 2026-08-07 16:35 UTCGHSA enrichment
  39. 2026-08-07 03:51 UTCGHSA enrichment
  40. 2026-08-06 15:07 UTCEG score recompute
  41. 2026-08-06 15:07 UTCGHSA enrichment
  42. 2026-08-06 13:46 UTCEPSS rescore
  43. 2026-08-06 02:19 UTCEG score recompute
  44. 2026-08-06 02:19 UTCGHSA enrichment
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-05 13:35 UTCEG score recompute
  47. 2026-08-05 13:35 UTCGHSA enrichment
  48. 2026-08-05 12:31 UTCEG score recompute
  49. 2026-08-05 12:31 UTCGHSA enrichment
  50. 2026-08-05 03:55 UTCEG score recompute
  51. 2026-08-05 03:55 UTCGHSA enrichment
  52. 2026-08-04 15:09 UTCEPSS rescore
  53. 2026-08-04 15:09 UTCEG score recompute
  54. 2026-08-04 15:09 UTCGHSA enrichment
  55. 2026-08-04 10:38 UTCEPSS rescore
  56. 2026-08-04 02:25 UTCGHSA enrichment
  57. 2026-08-03 13:41 UTCEG score recompute
  58. 2026-08-03 13:40 UTCGHSA enrichment
  59. 2026-08-03 12:41 UTCEG score recompute
  60. 2026-08-03 12:41 UTCGHSA enrichment
  61. 2026-08-03 10:35 UTCEPSS rescore
  62. 2026-08-03 07:55 UTCGHSA enrichment
  63. 2026-08-02 17:22 UTCGHSA enrichment
  64. 2026-08-02 04:38 UTCEG score recompute
  65. 2026-08-02 04:38 UTCGHSA enrichment
  66. 2026-08-02 02:26 UTCEPSS rescore
  67. 2026-08-01 15:54 UTCEG score recompute
  68. 2026-08-01 15:54 UTCGHSA enrichment
  69. 2026-08-01 04:15 UTCEPSS rescore
  70. 2026-08-01 03:10 UTCGHSA enrichment
  71. 2026-07-31 14:12 UTCGHSA enrichment
  72. 2026-07-31 01:11 UTCEG score recompute
  73. 2026-07-31 01:10 UTCGHSA enrichment
  74. 2026-07-30 16:27 UTCEPSS rescore
  75. 2026-07-30 12:23 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-11998?
CVE-2026-11998 is a high vulnerability published on June 24, 2026. A flaw in AngularJS' Strict Contextual Escaping (SCE) logic allows bypassing certain SCE policies for resource URLs and can lead to arbitrary JavaScript execution within the context of the victim's browser session. SCE's purpose is to ensure that only trusted or safe values are used in certain…
When was CVE-2026-11998 disclosed?
CVE-2026-11998 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11998 actively exploited?
CVE-2026-11998 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 59.3% of all scored CVEs.
What is the CVSS score of CVE-2026-11998?
CVE-2026-11998 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-11998?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11998, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-11998

Explore →

Is Your Infrastructure Affected by CVE-2026-11998?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs