CVE-2022-31776 [High] | Security Vulnerability in Datapower Gateway

IBM DataPower Gateway 10.0.2.0 through 10.0.4.0, 10.0.1.0 through 10.0.1.8, 10.5.0.0, and 2018.4.1.0 through 2018.4.1.21 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks. IBM X-Force ID: 228433.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.14%	0.44%	+0.31%
2	2025-08-15	0.17%	0.14%	-0.03%
3	2025-08-02	—	0.17%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.14%

0.44%

+0.31%

2025-08-15

0.17%

0.14%

-0.03%

2025-08-02

—

0.17%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]
6.5	3.0	MEDIUM	`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	3.9	2.5	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

6.5

3.0

MEDIUM

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

3.9

2.5

[email protected]

Affected software / configurations for CVE-2022-31776

Vendor	Product	Version	Raw CPE
ibm	datapower_gateway	>= 10.0.1.0, <= 10.0.1.8	cpe:2.3:a:ibm:datapower_gateway::::::::
ibm	datapower_gateway	>= 10.0.2.0, < 10.5.0.1	cpe:2.3:a:ibm:datapower_gateway:::::continuous_delivery:::*
ibm	datapower_gateway	>= 2018.4.1.0, <= 2018.4.1.21	cpe:2.3:a:ibm:datapower_gateway::::::::
ibm	datapower_gateway	10.5.0.0	cpe:2.3:a:ibm:datapower_gateway:10.5.0.0:::::::*

References for CVE-2022-31776

URL	Tags
https://exchange.xforce.ibmcloud.com/vulnerabilities/228433	VDB Entry Vendor Advisory
https://www.ibm.com/support/pages/node/6608604	Patch Vendor Advisory

URL

CVE-2022-31776

Exploit prediction scoring system (EPSS) score for CVE-2022-31776

Common vulnerability scoring system (CVSS) metrics for CVE-2022-31776

Weakness enumeration for CVE-2022-31776

Affected software / configurations for CVE-2022-31776

References for CVE-2022-31776