ManageIQ / ManageIQ/ui-components
CVE-2026-11998 (High) detected in angular-1.8.3.tgz
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Description
CVE-2026-11998 - High Severity Vulnerability
Vulnerable Library - angular-1.8.3.tgz
HTML enhanced for web apps
Library home page: https://registry.npmjs.org/angular/-/angular-1.8.3.tgz
Sample Path to Dependency File: /package.json
Path to vulnerable library: /home/wss-scanner/.yarn/berry/cache/angular-npm-1.8.3-0e5e833690-10.zip
Dependency Hierarchy:
- angular-ui-sortable-0.19.0.tgz (Root Library)
- ❌ angular-1.8.3.tgz (Vulnerable Library)
Found in HEAD commit: a5db0714038685437d759b29eb80b4b9e415b2c2
Found in base branch: master
Vulnerability Details
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, '<iframe>' 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 .
This is fixed in NES versions 1.9.12, 1.5.29 and 1.4.17.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2026-06-24
URL: CVE-2026-11998
CVSS 3 Score Details (7.6)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: Low
- Availability Impact: Low
Suggested Fix
Type: Upgrade version
Origin: https://www.herodevs.com/vulnerability-directory/cve-2026-11998
Release Date: 2026-06-24
Fix Resolution: angular - 1.5.11-angularjs-1.5.29,angular - 1.8.3-angularjs-1.9.12,angular - 1.5.11-angularjs-1.5.29,angular - 1.8.3-angularjs-1.9.12
Step up your Open Source Security Game with Mend here
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with package.json and inspect how angular-1.8.3.tgz enters the dependency tree through angular-ui-sortable-0.19.0.tgz. Update the dependency resolution to a listed fixed AngularJS/NES version, then verify the vulnerable 1.8.3 archive is no longer present in the dependency hierarchy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angularjs
- Domain
- frontend, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100