CVE-2025-56405: An issue was discovered in litmusautomation litmus-mcp-server thru 0.0.1 allowing unauthorized attackers to co

This week

HIGH 7.5REMOTEDOWNGRADE

CVE-2025-56405 is a high-severity flaw (CVSS 7.5) affecting mcp server. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in litmusautomation litmus-mcp-server thru 0.0.1 allowing unauthorized attackers to control the target's MCP service through the SSE protocol.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 75%)
CISA exploited list	No
Weakness	CWE-284, CWE-306
Published	2025-09-10
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: litmus

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-09-10 14:15 UTCPublished CVE record published
2026-06-17 09:42 UTCUpdated Record last modified

litmus mcp server DOWNGRADE

Affected: 0.0.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.0.1

1. Check installed version

apt-cache policy mcp-server || rpm -q mcp-server || mcp-server --version

2. No fixed release: DOWNGRADE to a release before 0.0.1 (Debian / Ubuntu)

apt-cache madison mcp-server sudo apt install mcp-server=<VERSION_BEFORE_0.0.1> sudo apt-mark hold mcp-server

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list mcp-server sudo dnf downgrade mcp-server-<VERSION_BEFORE_0.0.1> sudo dnf versionlock add mcp-server

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-56405?

mcp server: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-56405 being exploited?

CVE-2025-56405 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-56405 affect?

CVE-2025-56405 affects mcp server. Severity is high (CVSS 7.5). An issue was discovered in litmusautomation litmus-mcp-server thru 0.0.1 allowing unauthorized attackers to control the target's MCP service through the SSE protocol.

How urgent is CVE-2025-56405?

Priority 43/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-57300 MEDIUM 4.3 UPGRADE A missing permission check in Jenkins MCP Server Plugin 0.177.v629fdb_2557fe and earlier allows attackers with
CVE-2026-47427 HIGH 7.5 UPGRADE GitHub MCP Server is GitHub's official MCP Server
CVE-2025-64132 MEDIUM 5.4 UPGRADE Jenkins MCP Server Plugin 0.84.v50ca_24ef83f2 and earlier does not perform permission checks in multiple MCP t

References

← Back to latest CVEs