CVE-2025-2987: IBM Maximo Asset Management 7.6.1.3 is vulnerable to server-side request forgery (SSRF)

Routine

LOW 3.8DOWNGRADE

CVE-2025-2987 is a low-severity flaw (CVSS 3.8) affecting maximo asset management. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

IBM Maximo Asset Management 7.6.1.3 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.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	3.8 (Low)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.2% (top 87%)
CISA exploited list	No
Weakness	CWE-918
Published	2025-04-22
Last modified	2026-06-17

Publisher (CNA): IBM Corporation · Vendor: ibm

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-04-22 00:15 UTCPublished CVE record published
2026-06-17 09:07 UTCUpdated Record last modified

ibm maximo asset management DOWNGRADE

Affected: 7.6.1.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 7.6.1.3

1. Check installed version

apt-cache policy maximo-asset-management || rpm -q maximo-asset-management || maximo-asset-management --version

2. No fixed release: DOWNGRADE to a release before 7.6.1.3 (Debian / Ubuntu)

apt-cache madison maximo-asset-management sudo apt install maximo-asset-management=<VERSION_BEFORE_7.6.1.3> sudo apt-mark hold maximo-asset-management

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list maximo-asset-management sudo dnf downgrade maximo-asset-management-<VERSION_BEFORE_7.6.1.3> sudo dnf versionlock add maximo-asset-management

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-2987?

maximo asset management: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-2987 being exploited?

CVE-2025-2987 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-2987 affect?

CVE-2025-2987 affects maximo asset management. Severity is low (CVSS 3.8). IBM Maximo Asset Management 7.6.1.3 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 othe

How urgent is CVE-2025-2987?

Priority 16/100. No elevated risk signals yet.

Related CVEs

CVE-2025-2986 MEDIUM 5.5 DOWNGRADE IBM Maximo Asset Management 7.6.1.3 is vulnerable to stored cross-site scripting
CVE-2024-45652 MEDIUM 6.5 DOWNGRADE IBM Maximo MXAPIASSET API 7.6.1.3 could allow a remote attacker to traverse directories on the system
CVE-2024-45077 MEDIUM 6.5 DOWNGRADE IBM Maximo Asset Management 7.6.1.3 MXAPIASSET API is vulnerable to unrestricted file upload which allows auth
CVE-2024-22333 LOW 3.3 DOWNGRADE DOWNGRADE IBM Maximo Asset Management 7.6.1.3 and IBM Maximo Application Suite 8.10 and 8.11 allows web pages to be stor
CVE-2023-47718 MEDIUM 4.3 UPGRADE DOWNGRADE IBM Maximo Asset Management 7.6.1.3 and Manage Component 8.10 through 8.11 is vulnerable to cross-site request

References

← Back to latest CVEs