Security readout for executives and security teams
Plain-English summary
A flaw in jsonpath 1.1.1 may let untrusted input alter shared JavaScript object behavior through prototype pollution. In an exposed application, this could undermine security decisions, corrupt data, or disrupt service. Actual impact depends on how the library and affected function are used.
Executive priority
Treat confirmed reachable use as an urgent remediation item because the published score is critical and exploitation requires no stated privileges or interaction. First verify whether version 1.1.1 is deployed and exposed; prioritize reachable internet-facing or security-sensitive services. Do not infer compromise solely from package presence.
Technical view
The value function in jsonpath 1.1.1 lib/index.js is reported vulnerable to prototype pollution. The record assigns CVSS 3.1 score 9.8 with network access, low complexity, no privileges, and no user interaction. The supplied evidence does not establish which application inputs reach this function or confirm specific downstream effects.
Likely exposure
Prioritize applications containing jsonpath 1.1.1 where remote or otherwise untrusted data can influence JSONPath processing through the value function. The bundle provides no product inventory or CPE mapping, so installation and reachability must be established locally.
Exploitation context
The supplied bundle marks this CVE as absent from KEV and contains no cited assertion of active exploitation. This does not prove exploitation is absent. The CVSS vector describes a remotely reachable worst-case scenario, but practical exploitability depends on application data flow and library usage.
Researcher notes
The source bundle identifies CWE-1321 and CWE-502, but its concise description substantiates prototype pollution specifically. Affected vendor, product, CPE, fixed upstream version, and exploitation telemetry are not supplied. Red Hat errata indicate packaged remediation information exists, but applicability and exact corrected versions require consulting each advisory.
Mitigation direction
- Inventory direct and transitive installations of jsonpath 1.1.1.
- Review the listed Red Hat and upstream guidance for applicable corrected packages or versions.
- Upgrade using applicable vendor-supported updates after compatibility testing.
- Restrict untrusted input from reaching JSONPath evaluation until remediation is complete.
- Restart or redeploy affected processes after updating to clear polluted runtime state.
Validation and detection
- Confirm the deployed dependency tree no longer resolves jsonpath 1.1.1.
- Trace whether external input can reach the library's value function.
- Test security-sensitive object behavior in an isolated environment without offensive payloads.
- Verify vendor advisories applicable to each operating system or packaged application.
- Monitor for unexpected inherited properties, authorization changes, crashes, or configuration corruption.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-502: 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-2025-61140 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-01-28T17:00:46.678Z: Reported to Red Hat.
- 2026-01-28T00:00:00.000Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/dchester/jsonpathCVE reference, mitre
- https://gist.github.com/Dremig/8105c189774217222a8ebea3ed4d341dCVE reference, mitre
- https://access.redhat.com/security/cve/CVE-2025-61140CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2433946CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-61140.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:2181CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:3962CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:3960CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:6174CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:6802CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:2180CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
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.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.