CVE-2025-14684

Log record falsification via unneutralized message data

Published Mar 25, 2026 · Updated Mar 25, 2026

Log forging in IBM Maximo Monitor 8.10, 8.11, 9.0, and 9.1 allows local users to inject data into log messages. IBM attributes the flaw to improper neutralization of special elements when Monitor writes messages to log files but does not identify the affected input path or code locus. Local access is required, and crafted content can falsify recorded events without reported confidentiality or availability impact.

CVSS severity4.0
Medium
EPSS probability0.14%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Log forging in IBM Maximo Monitor 8.10, 8.11, 9.0, and 9.1 allows local users to inject data into log messages. IBM attributes the flaw to improper neutralization of special elements when Monitor writes messages to log files but does not identify the affected input path or code locus. Local access is required, and crafted content can falsify recorded events without reported confidentiality or availability impact.

The record

CVE
CVE-2025-14684
Published
Mar 25, 2026
Updated
Mar 25, 2026
Vendor
IBM
Product
Maximo Monitor
Classifications
CWE-117, T1565.001
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 25, 2026CVE publishedPublication date reported by the CVE source.
  2. Mar 25, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=8.10
  2. Affected versionversion=8.11
  3. Affected versionversion=9.0
  4. Affected versionversion=9.1

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

IBM · Maximo Monitorversion=8.10; version=8.11; version=9.0; version=9.1

Published CVSS scores

4.0IBMCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
3.3NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-117Improper Output Neutralization for Logs
T1565.001Stored Data Manipulation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo