Skip to main content
VulnerabilityPublished Updated

CVE-2025-55113: BMC Control-M/Agent · Improper Neutralization of Null Byte or NUL Character

Affects BMC Control-M/AgentSource CVE Database V5

0

Not known to be exploited · CVSS 9.5 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 4.0 base score
9.5Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
BMC Control-M/AgentAffected
  • 9.0.18 – 9.0.22.000
5 affected builds
Fixed in–

AI-suggested

  1. Immediately identify and inventory all instances of BMC Control-M/Agent running affected versions (9.0.18 to 9.0.22.000).
  2. Where possible, upgrade to the latest supported version of Control-M/Agent that does not use the vulnerable C router or has addressed this vulnerability.
  3. If upgrading is not immediately feasible, disable the C router by configuring the JAVA_AR setting to use a non-vulnerable routing method.
  4. Implement strict certificate validation policies and monitor for anomalous client certificates containing NULL bytes or other suspicious characters.
  5. Employ network segmentation and firewall rules to restrict access to Control-M/Agent interfaces to trusted hosts only.
  6. Monitor logs for failed or suspicious ACL checks and unusual job execution patterns.
  7. Engage with BMC support for official patches or workarounds as they become available.
  8. Conduct regular security assessments and penetration tests focusing on authentication and ACL enforcement mechanisms.
  9. Educate administrators about the risks of using outdated or unsupported software versions and the importance of timely patching.

Description

If the Access Control List is enforced by the Control-M/Agent and the C router is in use (default in Out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 and potentially earlier unsupported versions; non-default but configurable using the JAVA_AR setting in newer versions), the verification stops at the first NULL byte encountered in the email address referenced in the client certificate. An attacker could bypass configured ACLs by using a specially crafted certificate.

References

Community reviews

Loading reviews…