BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-77415High confidence

JSONata: Arbitrary Code Execution via crafted JSONata expressions

jsonata-js · jsonata

Official source article: GitHub GHSA-66MM-25PP-RFFF ↗. Check the applicable product and release in the original source.

9.3CriticalCVSS 4.0
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.89% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs jsonata-js jsonata and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmjsonata>= 2.0.0, < 2.2.12.2.1GitHub advisory ↗upstream repository advisory · 21 Aug 2026
npmjsonata< 1.8.81.8.8GitHub advisory ↗upstream repository advisory · 21 Aug 2026
npmjsonataSEMVER: introduced 2.0.0; fixed 2.2.12.2.1OSV record ↗aggregator derived · 21 Aug 2026
npmjsonataSEMVER: introduced 0; fixed 1.8.81.8.8OSV record ↗aggregator derived · 21 Aug 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-77415 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityjsonata: JSONata: Arbitrary Code Execution via crafted JSONata expressions
1 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • registry.redhat.io/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets@sha256:df55fd567640bcd54d8e0d19baa97a5e72429865ad342c94bb80c3a49a5c184e_amd64 as a component of Red Hat Developer Hub 1.10
Summary
A flaw was found in JSONata, a JSON query and transformation language. A remote attacker could exploit multiple object-integrity weaknesses by crafting malicious JSONata expressions. This could lead to arbitrary code execution with the privileges of the host process, allowing the attacker to take full control of the affected system.
Remediation
For more about Red Hat Developer Hub, see References links
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-64166

No EUVD known-exploited evidence

JSONata is a JSON query and transformation language. Prior to 1.8.8 and 2.2.1, crafted JSONata expressions could chain several object-integrity weaknesses to execute arbitrary code. The chain could overwrite $clone to mutate objects through evaluateTransformExpression, expose and deconstruct JSONata functions or lambdas through $merge.*, replace proc.arguments.forEach used by applyProcedure, and forge internal lambda state. These primitives allowed an attacker to reach prototype getters, prototype and constructor access, and process.getBuiltinModule with child_process, executing code with the privileges of the host process. This issue is fixed in versions 1.8.8 and 2.2.1.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
9.3 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

JSONata is a JSON query and transformation language. Prior to 1.8.8 and 2.2.1, crafted JSONata expressions could chain several object-integrity weaknesses to execute arbitrary code. The chain could overwrite $clone to mutate objects through evaluateTransformExpression, expose and deconstruct JSONata functions or lambdas through $merge.*, replace proc.arguments.forEach used by applyProcedure, and forge internal lambda state. These primitives allowed an attacker to reach prototype getters, prototype and constructor access, and process.getBuiltinModule with child_process, executing code with the privileges of the host process. This issue is fixed in versions 1.8.8 and 2.2.1.

What

JSONata is a JSON query and transformation language. Prior to 1.8.8 and 2.2.1, crafted JSONata expressions could chain several object-integrity weaknesses to execute arbitrary code. The chain could overwrite $clone to mutate objects through evaluateTransformExpression, expose and deconstruct JSONata functions or lambdas through $merge.*, replace proc.arguments.forEach used by applyProcedure, and forge internal lambda state. These primitives allowed an attacker to reach prototype getters, prototype and constructor access, and process.getBuiltinModule with child_process, executing code with the privileges of the host process. This issue is fixed in versions 1.8.8 and 2.2.1.

Why

Untrusted data can cross into a code-evaluation path and be interpreted as executable instructions.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

JSONata is a JSON query and transformation language. Prior to 1.8.8 and 2.2.1, crafted JSONata expressions could chain several object-integrity weaknesses to execute arbitrary code. The chain could overwrite $clone to mutate objects through evaluateTransformExpression, expose and deconstruct JSONata functions or lambdas through $merge.*, replace proc.arguments.forEach used by applyProcedure, and forge internal lambda state. These primitives allowed an attacker to reach prototype getters, prototype and constructor access, and process.getBuiltinModule with child_process, executing code with the privileges of the host process. This issue is fixed in versions 1.8.8 and 2.2.1.

Why

Untrusted data can cross into a code-evaluation path and be interpreted as executable instructions.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
a network path → Improper Control of Generation of Code ('Code Injection') → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-94 ↗

CWE-94: Improper Control of Generation of Code ('Code Injection'). The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-94Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-64166Official EUVD mapping

JSONata is a JSON query and transformation language. Prior to 1.8.8 and 2.2.1, crafted JSONata expressions could chain several object-integrity weaknesses to execute arbitrary code. The chain could overwrite $clone to mutate objects through evaluateTransformExpression, expose and deconstruct JSONata functions or lambdas through $merge.*, replace proc.arguments.forEach used by applyProcedure, and forge internal lambda state. These primitives allowed an attacker to reach prototype getters, prototype and constructor access, and process.getBuiltinModule with child_process, executing code with the privileges of the host process. This issue is fixed in versions 1.8.8 and 2.2.1.

Official EUVD record ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260826Security Bulletin 26 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 26 Aug 2026, published on 26 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-73088 Référence CVE CVE-2026-73089 https://www.cve.org/CVERecord?id=CVE-2026-73089 Référence CVE CVE-2026-73180 https://www.cve.org/CVERecord?id=CVE-2026-73180 Référence CVE CVE-2026-75595 https://www.cve.org/CVERecord?id=CVE-2026-75595 Référence CVE CVE-2026-75596 https://www.cve.org/CVERecord?id=CVE-2026-75596 Référence CVE CVE-2026-75838 https://www.cve.org/CVERecord?id=CVE-2026-75838 Référence CVE CVE-2026-77310 https://www.cve.org/CVERecord?id=CVE-2026-77310 Référence CVE CVE-2026-77413 https://www.cve.org/CVERecord?id=CVE-2026-77413 Référence CVE CVE-2026-77414 https://www.cve.org/CVERecord?id=CVE-2026-77414 Référence CVE CVE-2026-77415 https://www.cve.org/CVERecord?id=CVE-2026-77415 Référence CVE CVE-2026-8384 https://www.cve.org/CVERecord?id=CVE-2026-8384 Référence CVE CVE-2026-8400 https://www.cve.org/CVERecord?id=CVE-2026-8400 Référence CVE CVE-2026-84305 https://www.cve.org/CVERecord?id=CVE-2026-84305 Référence CVE CVE-2026-8484 https://www.cve.org/CVERecord?id=CVE-2026-8484 Référence CVE CVE-2026-86093 https://www.cve.org/CVERecord?id=CVE-2026-86093 Référence CVE CVE-2026-8620 https://www.cve.org/CVERecord?id=CVE-2026-8620 Référence CVE CVE-2026-8633 https://www.cve.org/CVERecord?id=CVE-2026-8633 Référence CVE CVE-2026-8646 https://www.cve.org/CVERecord?id=CVE-2026-86

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
jsonata: 2.0.0, < 2.2.1, < 1.8.8
Fixed
registry.redhat.io/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets@sha256:df55fd567640bcd54d8e0d19baa97a5e72429865ad342c94bb80c3a49a5c184e_amd64 as a component of Red Hat Developer Hub 1.10
Action
For more about Red Hat Developer Hub, see References links
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 21 Aug 2026 · Last source change 25 Aug 2026, 16:55 UTC · CWE-94 · Improper Control of Generation of Code ('Code Injection')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-23
European sourceENISA EUVD · EUVD-2026-64166
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    jsonata: < 1.8.8, >= 2.0.0, < 2.2.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    jsonata: < 1.8.8, >= 2.0.0, < 2.2.1 · Fixed: For more about Red Hat Developer Hub, see References links
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 1.8.8; >= 2.0.0, < 2.2.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 1.8.8; >= 2.0.0, < 2.2.1 · Fixed: For more about Red Hat Developer Hub, see References links
    Red Hat Product Security ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  4. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-77415 to remediation: access.redhat.com/CVE-2026-77415.
    Before
    remediation: access.redhat.com/CVE-2026-77415
    After
    remediation: access.redhat.com/CVE-2026-77415
    Red Hat Product Security ↗
  5. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets as a component of Red Hat Developer Hub
    After
    Fixed: registry.redhat.io/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets@sha256:df55fd567640bcd54d8e0d19baa97a5e72429865ad342c94bb80c3a49a5c184e_amd64 as a component of Red Hat Developer Hub 1.10
    Red Hat Product Security ↗
  7. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-77415 to remediation: access.redhat.com/CVE-2026-77415.
    Before
    remediation: access.redhat.com/CVE-2026-77415
    After
    remediation: access.redhat.com/CVE-2026-77415
    Red Hat Product Security ↗
  8. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Red Hat Product Security ↗
  9. Affected versionsThe structured affected or fixed version information changed.
    Before
    After
    rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets as a component of Red Hat Developer Hub
    Red Hat Product Security ↗
  10. Affected versionsThe structured affected or fixed version information changed.
    Before
    jsonata: < 1.8.8, >= 2.0.0, < 2.2.1 · Fixed: For more about Red Hat Developer Hub, see References links
    After
    jsonata: < 1.8.8, >= 2.0.0, < 2.2.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  11. Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/CVE-2026-77415.
    Before
    remediation: access.redhat.com/CVE-2026-77415
    After
    no authoritative guidance recorded
    CNA ↗
  12. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 1.8.8; >= 2.0.0, < 2.2.1 · Fixed: For more about Red Hat Developer Hub, see References links
    After
    jsonata: < 1.8.8, >= 2.0.0, < 2.2.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  13. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
  14. BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.
    Before
    no BlackTree article
    After
    1 BlackTree article
    BlackTree editorial ↗
  15. ENISA EUVD mappingEUVD-2026-64166 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-64166"}
    ENISA EUVD ↗
  16. Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.
    Before
    No public exploit
    After
    Public exploit reference
    CVE.org ↗
  17. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-64166↗Red Hat Product Security security advisory↗CISA Vulnrichment SSVC evidence↗CVE authority or vendor reference · GitHub GHSA-66MM-25PP-RFFF↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-77415 · cve.blacktree.nl