PULSE
FEED
ransombarracuda reclama a Dallas Fort Worth Fertility Associates · US · Healthcareransompear reclama a Law Office of Ronald D. Weiss, P.C · US · Professional Servicesransomeclipse reclama a Realta Technologies · IE · Technologyransominception reclama a Lucid Motors · US · Manufacturingransomwhitearmor reclama a DROP 1 — CASANARE, PAJONAL, PUTUMAYO AND URUS — 8,000 PATIENTS, 4,000 INVOICES, 7,733 CRED... · CO · Healthcareransompixelleaks reclama a MT5 algo-trading farm (OneFunded funded account, WINSERVER) · Financial Servicesransompixelleaks reclama a bastion.internal domain controller (GCP, GRATEFUL-V1) · Technologyransompixelleaks reclama a Aixia Group AB (Nasdaq-listed AI/IT, Sweden) · SE · Technologyransompixelleaks reclama a Kingsport Cargo (logistics, Laravel intranet) · Transportationransompixelleaks reclama a Arab Software Computer / ASCON (Oracle ERP hosting, Alexandria) · EG · Technologyransommedusalocker reclama a Lee Memorial Health System · US · Healthcareransomeverest reclama a FAST ČR · CZ · Government & Defenseransomeverest reclama a Alla France · FR · Otherransomeverest reclama a ABL Bio · Healthcareransombarracuda reclama a Dallas Fort Worth Fertility Associates · US · Healthcareransompear reclama a Law Office of Ronald D. Weiss, P.C · US · Professional Servicesransomeclipse reclama a Realta Technologies · IE · Technologyransominception reclama a Lucid Motors · US · Manufacturingransomwhitearmor reclama a DROP 1 — CASANARE, PAJONAL, PUTUMAYO AND URUS — 8,000 PATIENTS, 4,000 INVOICES, 7,733 CRED... · CO · Healthcareransompixelleaks reclama a MT5 algo-trading farm (OneFunded funded account, WINSERVER) · Financial Servicesransompixelleaks reclama a bastion.internal domain controller (GCP, GRATEFUL-V1) · Technologyransompixelleaks reclama a Aixia Group AB (Nasdaq-listed AI/IT, Sweden) · SE · Technologyransompixelleaks reclama a Kingsport Cargo (logistics, Laravel intranet) · Transportationransompixelleaks reclama a Arab Software Computer / ASCON (Oracle ERP hosting, Alexandria) · EG · Technologyransommedusalocker reclama a Lee Memorial Health System · US · Healthcareransomeverest reclama a FAST ČR · CZ · Government & Defenseransomeverest reclama a Alla France · FR · Otherransomeverest reclama a ABL Bio · Healthcare
← All CVEs
CVE WatchNov 21, 2026

CVE-2025-42884

SAP NetWeaver Improper Neutralization of Special Elements in Data Query Logic Vulnerability

CVSS

6.5

Medium

EPSS

0.3%

p20

KEV

YES

Nov 20, 2026

Exploit Today

56

0-100

Published: Nov 11, 2025 · Last modified: Nov 21, 2026 · CWE-943

EPSS · 30d
0.3%EPSS · 30 days0.3%
2026-10-232026-11-20
KEV catalog record

Product

SAP / NetWeaver

Vulnerability

SAP NetWeaver Improper Neutralization of Special Elements in Data Query Logic Vulnerability

Added to KEV

Nov 20, 2026

Remediate by

Nov 23, 2026

Known ransomware use

No

Summary description

SAP NetWeaver Enterprise Portal contains an improper neutralization of special elements in data query logic vulnerability that allows an unauthenticated attacker to disclose or modify server information via injected JNDI environment properties or a URL used during JNDI lookup operations.

Required action

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Notes

https://support.sap.com/en/my-support/knowledge-base/security-notes-news/bulletin-2025.html ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2025-42884

Technical description

SAP NetWeaver Enterprise Portal allows an unauthenticated attacker to inject JNDI environment properties or pass a URL used during JNDI lookup operations, enabling access to an unintended JNDI provider.�This could further lead to disclosure or modification of information about the server. There is no impact on availability.

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-125080—
53.4%
——16Improper neutralization of special elements in data query logic (Cypher injection) in the orderBy placeholder handling for custom queries in Neo4j Spring Data Neo4j versions 6.1.0 through 8.0.8 and 8.1.0 through 8.1.2 allows a remote attacker to read database contents via blind reads, write read content into new nodes, or, if APOC and APOC file export are enabled, to write query results to a file in the database's accessible file system via crafted sort order parameters. Exploitation requires an application that passes unvalidated user input as the orderBy value to a custom Cypher query using the placeholder directive.18h
CVE-2026-765435.4 MED
8.0%
——2In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could store attacker-controlled Search Processing Language (SPL) in a shared data model. The vulnerability is possible because the Data Model Editor does not properly neutralize data model field names when it builds a preview search. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The attacker should not be able to exploit the vulnerability at will. For more information see Add a regular expression field (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/define-data-model-dataset-fields/add-a-regular-expression-field), Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities), and About the search language (https://help.splunk.com/en/splunk-enterprise/search/search-manual/10.4/search-overview/about-the-search-language) in the Splunk documentation.2d
CVE-2026-765425.9 MED
12.3%
——4In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could trick a user who has an active Splunk Web session into selecting the Top values by time field report on the Search page. The selection could run arbitrary Search Processing Language (SPL) searches and potentially expose stored credentials and indexed data. The vulnerability is possible because Splunk Web does not correctly neutralize user-controlled data when it generates an SPL search for a field report. The vulnerability requires the attacker to phish the user by tricking them into opening a link that the attacker creates. The unauthenticated user should not be able to exploit the vulnerability at will.2d
CVE-2026-765388.8 HIG
35.6%
——11In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could cause Splunk Enterprise to run arbitrary Search Processing Language (SPL) searches with elevated privileges through data model acceleration. The vulnerability is possible because Splunk Enterprise does not correctly neutralize caller-supplied data model acceleration values before it places them into generated summarization searches.1d
CVE-2026-1312397.3 HIG
24.7%
——7In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in Updates data. If another user who can access the System Update Status report selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data and modify data available to the user who selects the row. The vulnerability is possible because the System Update Status report does not validate destination, signature, and vendor-product values before inserting them into drilldown searches. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and System Update Status (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/system-update-status) in the Splunk documentation.9h
CVE-2026-1312386.4 MED
3.3%
——1In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled certificate values. If another user who can access the Secure Sockets Layer Search dashboard selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data and modify data available to the user who selects the row. The vulnerability is possible because the Secure Sockets Layer Search dashboard encodes certificate values for the drilldown link but does not escape the values as SPL search literals before inserting the values into drilldown searches. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and Protocol intelligence dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/protocol-intelligence-dashboards) in the Splunk documentation.9h