SAPCAR - version 7.22, does not contain sufficient input validation on the SAPCAR archive.

published 2022-03-08 4y ago modified 2026-06-17 4mo ago also EUVD-2022-30668

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.2%; EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits: 0; none known

SAPCAR - version 7.22, does not contain sufficient input validation on the SAPCAR archive. As a result, the SAPCAR process may crash, and the attacker may obtain privileged access to the system.

Is CVE-2022-26100 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

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

SAP SE SAPCAR

Classification

Weakness

CWE-129 Improper Validation of Array Index
CWE-20 Improper Input Validation

References

launchpad.support.sap.com /#/notes/3111110
permissions-required, vendor-advisory
dam.sap.com /mac/embed/public/pdf/a/ucQrx6G.htm?rc=10
vendor-advisory

Sources

CVE List CVE-2022-26100
NVD CVE-2022-26100

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.