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
Elevated
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.6Exploit: Elevated riskExposed services: Not assessed

A fixed version is listed under Patch Availability — apply it.

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.6HIGHmedium confidence
EG Risk
50
EG Risk 50/100

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%
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Fixed version listed under Patch Availability.
genericMentions a patch (unverified)🟡 PoC Available

Vulnerability Directory | CVE-2026-11998 | AngularJS

https://www.herodevs.com/vulnerability-directory/cve-2026-11998?nes-for-angularjs
genericMentions a patch (unverified)🟡 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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
angular.js1.8.2-2, 1.8.3-1, 1.8.3-2, 1.8.3-3
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-1, 1.8.3-1+deb12u1, 1.8.3-1+deb12u1~deb11u1, 1.8.3-2, 1.8.3-3
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-3
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-3
  • every version on: no fix on record
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
angular—
  • 1.2.0-rc.3 through 1.8.3: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 245 total refreshes for this CVE.

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

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 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 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11998?
CVE-2026-11998 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-11998?
A fixed version for CVE-2026-11998 is listed under Patch Availability on this page: update to the version listed for your package. The vendor advisories EchelonGraph has for CVE-2026-11998 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs