IBM Maximo Anywhere 7.6.4.0 could allow an attacker to reverse engineer the application due to the lack of binary protection precautions.

published 2022-02-16 4y ago modified 2026-06-17 4mo ago also EUVD-2019-13898

cvss: 6.5; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 39%
public exploits: 0; none known

IBM Maximo Anywhere 7.6.4.0 could allow an attacker to reverse engineer the application due to the lack of binary protection precautions. IBM X-Force ID: 160697.

Is CVE-2019-4291 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

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

CVSS scores

assigned by	version	score	vector
CNA	3.0	6.5	CVSS:3.0/S:U/A:N/UI:N/AV:N/C:L/PR:N/AC:L/I:L/RC:C/RL:O/E:U
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CNA	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
NVD	2.0	6.4	AV:N/AC:L/Au:N/C:P/I:P/A:N

Affected products

IBM Maximo Anywhere

Classification

Weakness

CWE-326 Inadequate Encryption Strength

References

ibm.com /support/pages/node/6556834
vendor-advisory
exchange.xforce.ibmcloud.com /vulnerabilities/160697
vdb-entry, vendor-advisory

Sources

CVE List CVE-2019-4291
NVD CVE-2019-4291

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.