How severe is CVE-2025-3357?

CVE-2025-3357 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-3357 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (53rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-3357?

CVE-2025-3357 primarily affects Ibm Tivoli Monitoring. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2025-3357?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2025-3357 have an EU (EUVD) identifier?

Yes. CVE-2025-3357 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-16283.

When was CVE-2025-3357 published?

CVE-2025-3357 was published on 2025-05-28 and last updated on 2026-06-17.

CVE-2025-3357

CVE-2025-3357 is a critical-severity vulnerability in Ibm Tivoli Monitoring with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-129.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 1% (53rd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-16283
Weakness: CWE-129
Affected product: Ibm Tivoli Monitoring
Published: 2025-05-28
Last modified: 2026-06-17

Description

IBM Tivoli Monitoring 6.3.0.7 through 6.3.0.7 Service Pack 19 could allow a remote attacker to execute arbitrary code due to improper validation of an index value of a dynamically allocated array.

Frequently asked questions

What is CVE-2025-3357?: IBM Tivoli Monitoring 6.3.0.7 through 6.3.0.7 Service Pack 19 could allow a remote attacker to execute arbitrary code due to improper validation of an index value of a dynamically allocated array.
How severe is CVE-2025-3357?: CVE-2025-3357 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-3357 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (53rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-3357?: CVE-2025-3357 primarily affects Ibm Tivoli Monitoring. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-3357?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-3357 have an EU (EUVD) identifier?: Yes. CVE-2025-3357 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-16283.
When was CVE-2025-3357 published?: CVE-2025-3357 was published on 2025-05-28 and last updated on 2026-06-17.

References

https://www.ibm.com/support/pages/node/7234923

Affected products (2)

cpe:2.3:a:ibm:tivoli_monitoring:6.3.0.7:-:*:*:*:*:*:*
cpe:2.3:a:ibm:tivoli_monitoring:6.3.0.7:sp19:*:*:*:*:*:*

More vulnerabilities in Ibm Tivoli Monitoring

CVE-2015-7411 — Critical (CVSS 9.9): The portal client in IBM Tivoli Monitoring (ITM) 6.2.2 through FP9, 6.2.3 through FP5, and 6.3.0 through FP6 allows…
CVE-2017-1789 — Critical (CVSS 9.8): IBM Tivoli Monitoring V6 6.2.3 and 6.3.0 could allow an unauthenticated user to remotely execute code through…
CVE-2012-4823 — Critical (CVSS 9.3): Unspecified vulnerability in the JRE component in IBM Java 7 SR2 and earlier, Java 6.0.1 SR3 and earlier, Java 6 SR11…
CVE-2012-4822 — Critical (CVSS 9.3): Multiple unspecified vulnerabilities in the JRE component in IBM Java 7 SR2 and earlier, Java 6.0.1 SR3 and earlier,…
CVE-2012-4821 — Critical (CVSS 9.3): Multiple unspecified vulnerabilities in the JRE component in IBM Java 7 SR2 and earlier, Java 6.0.1 SR3 and earlier,…
CVE-2012-4820 — Critical (CVSS 9.3): Unspecified vulnerability in the JRE component in IBM Java 7 SR2 and earlier, Java 6.0.1 SR3 and earlier, Java 6 SR11…

All CVEs affecting Ibm Tivoli Monitoring →

Other CWE-129 (Improper Validation of Array Index) vulnerabilities

CVE-2020-27485 — Critical (CVSS 9.9): Garmin Forerunner 235 before 8.20 is affected by: Array index error. The component is: ConnectIQ TVM. The attack vector…
CVE-2020-27483 — Critical (CVSS 9.9): Garmin Forerunner 235 before 8.20 is affected by: Array index error. The component is: ConnectIQ TVM. The attack vector…
CVE-2026-21413 — Critical (CVSS 9.8): A heap-based buffer overflow vulnerability exists in the lossless_jpeg_load_raw functionality of LibRaw Commit 0b56545…
CVE-2025-27034 — Critical (CVSS 9.8): Memory corruption while selecting the PLMN from SOR failed list.
CVE-2024-45569 — Critical (CVSS 9.8): Memory corruption while parsing the ML IE due to invalid frame content.
CVE-2024-38623 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Use variable length array instead of…

Browse all CWE-129 (Improper Validation of Array Index) vulnerabilities →