Security advisory
angular-expressions is "angular's nicest part extracted as a standalone module for the browser and node". In angular-expressions before version 1.1.2 there is a vulnerability which allows Remote Code Execution if you call "expressions.compile(userControlledInput)" where "userControlledInput" is text that comes from user input. The security of the package could be bypassed by using a more complex payload, using a ".constructor.constructor" technique. In terms of impact: If running angular-expressions in the browser, an attacker could run any browser script when the application code calls expressions.compile(userControlledInput). If running angular-expressions on the server, an attacker could run any Javascript expression, thus gaining Remote Code Execution. This is fixed in version 1.1.2 of angular-expressions A temporary workaround might be either to disable user-controlled input that will be fed into angular-expressions in your application or allow only following characters in the userControlledInput.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2021-21277
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 11:31 UTC · Revision 1
Source evidence
angular-expressions is "angular's nicest part extracted as a standalone module for the browser and node". In angular-expressions before version 1.1.2 there is a vulnerability which allows Remote Code Execution if you call "expressions.compile(userControlledInput)" where "userControlledInput" is text that comes from user input. The security of the package could be bypassed by using a more complex payload, using a ".constructor.constructor" technique. In terms of impact: If running angular-expressions in the browser, an attacker could run any browser script when the application code calls expressions.compile(userControlledInput). If running angular-expressions on the server, an attacker could run any Javascript expression, thus gaining Remote Code Execution. This is fixed in version 1.1.2 of angular-expressions A temporary workaround might be either to disable user-controlled input that will be fed into angular-expressions in your application or allow only following characters in the userControlledInput.
osv:CVE-2021-21277
Complete source record
{
"id": "291d3e743304a33fee0631311ab37cc63c81533c4bddabf110452c5ca8be2977",
"url": "https://osv.dev/vulnerability/CVE-2021-21277",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2021-21277",
"summary": "angular-expressions is \"angular's nicest part extracted as a standalone module for the browser and node\". In angular-expressions before version 1.1.2 there is a vulnerability which allows Remote Code Execution if you call \"expressions.compile(userControlledInput)\" where \"userControlledInput\" is text that comes from user input. The security of the package could be bypassed by using a more complex payload, using a \".constructor.constructor\" technique. In terms of impact: If running angular-expressions in the browser, an attacker could run any browser script when the application code calls expressions.compile(userControlledInput). If running angular-expressions on the server, an attacker could run any Javascript expression, thus gaining Remote Code Execution. This is fixed in version 1.1.2 of angular-expressions A temporary workaround might be either to disable user-controlled input that will be fed into angular-expressions in your application or allow only following characters in the userControlledInput.",
"evidence": "osv:CVE-2021-21277",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2021-21277",
"aliases": [
"CVE-2021-21277",
"GHSA-j6px-jwvv-vpwq"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/peerigon/angular-expressions",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "3e4f0b437c33f57ba8f13e4197242740ff555aa0"
},
{
"fixed": "07edb62902b1f6127b3dcc013da61c6316dd0bf1"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:peerigon:angular-expressions:*:*:*:*:*:node.js:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "1.1.2"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "07edb62902b1f6127b3dcc013da61c6316dd0bf1"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v1.1.1",
"v1.1.0",
"v1.0.1",
"v1.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2021-21277.json"
}
}
],
"modified": "2026-10-20T10:54:27.868618406Z",
"provider": "osv",
"references": [
"https://www.npmjs.com/package/angular-expressions",
"https://github.com/peerigon/angular-expressions/security/advisories/GHSA-j6px-jwvv-vpwq",
"https://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1"
],
"provider_metadata": {}
},
"related_cves": [
{
"value": "CVE-2021-21277",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 385387,
"published_at": "2021-02-01T15:15:13.34+00:00"
}