CVE-2024-40582: Pentaminds CuroVMS v2.0.1 was discovered to contain exposed sensitive information.

This week

HIGH 7.5REMOTEDOWNGRADE

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

Pentaminds CuroVMS v2.0.1 was discovered to contain exposed sensitive information.

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 76%)
CISA exploited list	No
Weakness	CWE-312
Published	2024-12-09
Last modified	2026-07-05

Publisher (CNA): MITRE · Vendor: pentaminds

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

Am I affected?

Timeline

2024-12-09 16:15 UTCPublished CVE record published
2026-07-05 18:16 UTCUpdated Record last modified

pentaminds curovms DOWNGRADE

Affected: 2.0.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.1

1. Check installed version

apt-cache policy curovms || rpm -q curovms || curovms --version

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

apt-cache madison curovms sudo apt install curovms=<VERSION_BEFORE_2.0.1> sudo apt-mark hold curovms

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

dnf --showduplicates list curovms sudo dnf downgrade curovms-<VERSION_BEFORE_2.0.1> sudo dnf versionlock add curovms

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-2024-40582?

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

Is CVE-2024-40582 being exploited?

CVE-2024-40582 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-2024-40582 affect?

CVE-2024-40582 affects curovms. Severity is high (CVSS 7.5). Pentaminds CuroVMS v2.0.1 was discovered to contain exposed sensitive information.

How urgent is CVE-2024-40582?

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

Related CVEs

CVE-2024-40583 CRITICAL 9.1 DOWNGRADE Pentaminds CuroVMS v2.0.1 was discovered to contain exposed credentials.

References

← Back to latest CVEs