Analyst readout for executives and security teams
Plain-English summary
CVE-2026-12208 is a prototype pollution issue in the jsonata JavaScript library through version 2.2.0. A remote, unauthenticated attacker may be able to alter object prototype attributes when affected functionality processes attacker-controlled input. Public exploit material is referenced, but the provided sources do not show confirmed active exploitation.
Executive priority
Treat this as a near-term dependency risk, not an emergency unless jsonata processes external input in production. Prioritize internet-facing or multi-tenant applications first. The absence of a named vendor fix increases the need for inventory, exposure reduction, and monitoring.
Technical view
The reported flaw affects createFrame in src/jsonata.js within jsonata’s Function Binding Frame System. VulDB maps it to CWE-1321 and CWE-94, with CVSS 4.0 score 6.9. The source bundle lists jsonata 2.0, 2.1, and 2.2.0 as affected and describes low-complexity, network-reachable exploitation without privileges or user interaction.
Likely exposure
Exposure is most likely in Node.js or browser applications embedding jsonata 2.0 through 2.2.0, especially where untrusted users can influence JSONata expressions, bindings, or evaluated data. Systems using jsonata only on trusted internal input may have lower practical exposure.
Exploitation context
The vulnerability is described as remotely initiable and public exploit material is linked. The bundle says the vendor did not respond, and no official patch or mitigation is named. KEV status is false, and the sources provided do not confirm in-the-wild exploitation.
Researcher notes
Evidence is currently centered on VulDB and a linked public exploit repository. The report states vendor non-response and does not provide an official fix. Avoid assuming impact beyond prototype pollution unless confirmed in the specific application context, because exploitability depends on how jsonata is embedded and exposed.
Mitigation direction
- Inventory applications and packages using jsonata versions up to 2.2.0.
- Check jsonata-js vendor guidance and package releases for a fixed version.
- Restrict untrusted users from supplying JSONata expressions or binding data.
- Add input validation and isolation around JSONata evaluation paths.
- Monitor dependency advisories for updated remediation instructions.
Validation and detection
- Review dependency manifests and lockfiles for jsonata 2.0, 2.1, or 2.2.0.
- Identify application features that evaluate user-controlled JSONata input.
- Confirm whether affected code paths are internet-facing or externally reachable.
- Check security monitoring for unusual behavior around JSONata evaluation endpoints.
- Track CVE, VulDB, and repository updates for patch status changes.
Public sources used
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1321: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-12208 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
4 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P — — VulDB CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:P/RL:X/RC:R 3.9 1.4 VulDB CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:P/RL:X/RC:R 3.9 1.4 VulDB AV:N/AC:L/Au:N/C:N/I:P/A:N/E:POC/RL:ND/RC:UR 10 2.9 VulDB Vulnerability scoring details
Base CVSS 4.0 score
6.9 MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
Base CVSS 3.1 score
5.3 MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:P/RL:X/RC:R
Base CVSS 3.0 score
5.3 MediumVector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:P/RL:X/RC:R
Base CVSS 2.0 score
5 MediumVector: AV:N/AC:L/Au:N/C:N/I:P/A:N/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timeline VulDB
Advisory disclosed
- Source timeline VulDB
VulDB entry created
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- Source timeline VulDB
VulDB entry last update
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 source CVE List V5
- VDB-370850 | jsonata-js jsonata Function Binding Frame System jsonata.js createFrame prototype pollution CVE reference, VulDB · vdb-entry, technical-description
- VDB-370850 | CTI Indicators (IOB, IOC, TTP, IOA) CVE reference, VulDB · signature, permissions-required
- CVE-2026-12208 | CVE Analysis and Report CVE reference, VulDB · third-party-advisory
- Submit #832446 | jsonata-js jsonata 2.2.0 Prototype Pollution CVE reference, VulDB · third-party-advisory
- https://github.com/OriginSecurityX/jsonata-hasownproperty-bypass CVE reference, VulDB · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.