How severe is CVE-2025-55114?

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

Is CVE-2025-55114 being actively exploited?

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

How do I fix CVE-2025-55114?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

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

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

When was CVE-2025-55114 published?

CVE-2025-55114 was published on 2025-09-16 and last updated on 2026-06-17.

CVE-2025-55114

CVE-2025-55114 is a medium-severity vulnerability with a CVSS 3.x base score of 5.3. 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-696.

Key facts

Severity: Medium (CVSS 3.x base score 5.3)
CVSS v4: 6.9
EPSS exploit prediction: 0% (28th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-29568
Weakness: CWE-696
Published: 2025-09-16
Last modified: 2026-06-17

Description

The improper order of AUTHORIZED_CTM_IP validation in the Control-M/Agent, where the Control-M/Server IP address is validated only after the SSL/TLS handshake is completed, exposes the Control-M/Agent to vulnerabilities in the SSL/TLS implementation under certain non-default conditions (e.g. CVE-2025-55117 or CVE-2025-55118) or potentially to resource exhaustion.

Frequently asked questions

What is CVE-2025-55114?: The improper order of AUTHORIZED_CTM_IP validation in the Control-M/Agent, where the Control-M/Server IP address is validated only after the SSL/TLS handshake is completed, exposes the Control-M/Agent to vulnerabilities in the SSL/TLS implementation under certain non-default conditions (e.g. CVE-2025-55117 or CVE-2025-55118) or potentially to resource exhaustion.
How severe is CVE-2025-55114?: CVE-2025-55114 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability low.
Is CVE-2025-55114 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-55114?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-55114 have an EU (EUVD) identifier?: Yes. CVE-2025-55114 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-29568.
When was CVE-2025-55114 published?: CVE-2025-55114 was published on 2025-09-16 and last updated on 2026-06-17.

References

Other CWE-696 vulnerabilities

CVE-2026-45033 — High (CVSS 7.8): GitHub Copilot CLI brings AI-powered coding assistance directly to your command line. Prior to 1.0.43, a security…
CVE-2025-31485 — High (CVSS 7.5): API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. Prior to 4.0.22 and 3.4.17, a GraphQL…
CVE-2021-22569 — High (CVSS 7.5): An issue in protobuf-java allowed the interleaving of com.google.protobuf.UnknownFieldSet fields in such a way that…
CVE-2021-31379 — High (CVSS 7.5): An Incorrect Behavior Order vulnerability in the MAP-E automatic tunneling mechanism of Juniper Networks Junos OS…
CVE-2026-35637 — High (CVSS 7.3): OpenClaw before 2026.3.22 performs cite expansion before completing channel and DM authorization checks, allowing cite…
CVE-2024-24853 — High (CVSS 7.2): Incorrect behavior order in transition between executive monitor and SMI transfer monitor (STM) in some Intel(R)…

Browse all CWE-696 vulnerabilities →