An unauthenticated user can attach to an open interface exposed through JNDI by the Messaging System of SAP NetWeaver Process Integration (…

published 2022-12-13 3y ago modified 2026-06-17 4mo ago also EUVD-2022-44480

cvss: 9.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits: 0; none known

An unauthenticated user can attach to an open interface exposed through JNDI by the Messaging System of SAP NetWeaver Process Integration (PI) - version 7.50. This user can make use of an open naming and directory API to access services that could perform unauthorized operations. The vulnerability affects local users and data, leading to a considerable impact on confidentiality as well as availability and a limited impact on the integrity of the application. These operations can be used to:

* Read any information * Modify sensitive information * Denial of Service attacks (DoS) * SQL Injection

Is CVE-2022-41271 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: last yr. (2025-04-22)

Exploit prediction

0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.4	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H
NVD	3.1	9.4	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H

Affected products

SAP NetWeaver Process Integration

Classification

Weakness

CWE-862 Missing Authorization
CWE-306 Missing Authentication for Critical Functionality
CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

launchpad.support.sap.com /#/notes/3267780
permissions-required, vendor-advisory
sap.com /documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html
vendor-advisory

Sources

CVE List CVE-2022-41271
NVD CVE-2022-41271

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.