CVE-2026-44643
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 Expressions provides expressions for the Angular.JS web framework as a standalone module. Prior to 1.5.2, an attacker can write a malicious expression using filters that escapes the sandbox to execute arbitrary code on the system. This vulnerability is fixed in 1.5.2.
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 confidenceAngular Expressions, a standalone module for AngularJS-style expressions, contains a sandbox escape vulnerability in versions prior to 1.5.2. Attackers can craft malicious expressions using filters to break out of the sandbox and execute arbitrary code on the host system.
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< 1.5.2CVSS 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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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 installed Angular Expressions versionRun 'npm list angular-expressions' or inspect the package.json dependencies for the angular-expressions entryAffected if The listed version is lower than 1.5.2 (e.g., 1.5.1, 1.5.0, 1.4.x, etc.)
-
Verify the application uses expression evaluationSearch codebase for calls to 'angularExpressions.compile()', 'angularExpressions.evaluate()', or similar evaluation functions that process user-provided expressionsAffected if The application evaluates expressions using this module with input that could be influenced by external users
-
Identify if sandbox mode is enabledInspect the code where expression evaluation occurs - check if the 'sandbox' option is set to true or if the default sandbox is in useAffected if The code relies on the sandbox to restrict expression capabilities while processing untrusted input
You are affected if Angular Expressions version is below 1.5.2 AND your application uses this module to evaluate untrusted or user-provided expressions.
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 · scoped1.5.2
Upgrade to Angular Expressions version 1.5.2 or later to patch the sandbox escape vulnerability.
1.5.2
- Check current version of angular-expressions in your project by examining package.json or running npm list angular-expressions
- Update the angular-expressions dependency in package.json to require version 1.5.2 or higher (e.g., "angular-expressions": ">=1.5.2")
- Run npm install or yarn install to update the dependency to the fixed version
- Verify the updated version is installed by running npm list angular-expressions
- Test your application thoroughly to ensure the sandbox escape is prevented and no functionality is broken
- Rebuild and redeploy your application with the patched dependency
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44643 — 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-44643 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