Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-6107: Due to insufficient verification, an attacker could use a malicious client to bypass authentication checks and

48
This month
CRITICAL 9.6UPGRADE

CVE-2024-6107 is a critical-severity flaw (CVSS 9.6) affecting metal as a service. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Due to insufficient verification, an attacker could use a malicious client to bypass authentication checks and run RPC commands in a region. This has been addressed in MAAS and updated in the corresponding snaps.

Why this priority

  • Critical severity
  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score9.6 (Critical)
Attack vectorAdjacent network
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.4% (top 64%)
CISA exploited listNo
WeaknessCWE-287
Published2025-07-21
Last modified2026-06-17
Publisher (CNA): Canonical Ltd. · Vendor: canonical

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

canonical metal as a service UPGRADE
Affected: >= 3.1.0 and < 3.1.4 · >= 3.2.0 and < 3.2.11 · >= 3.3.0 and < 3.3.8 · >= 3.4.0 and < 3.4.4 · 3.5.0
Fixed in: 3.1.4, 3.2.11, 3.3.8, 3.4.4
Safe to downgrade to: a release before 3.1.0
1. Check installed version
apt-cache policy metal-as-a-service || rpm -q metal-as-a-service || metal-as-a-service --version
2. UPGRADE to 3.1.4 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade metal-as-a-service
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade metal-as-a-service
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.1.0 (Debian / Ubuntu)
apt-cache madison metal-as-a-service sudo apt install metal-as-a-service=<VERSION_BEFORE_3.1.0> sudo apt-mark hold metal-as-a-service
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list metal-as-a-service sudo dnf downgrade metal-as-a-service-<VERSION_BEFORE_3.1.0> sudo dnf versionlock add metal-as-a-service
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-6107?

metal as a service: upgrade to 3.1.4, 3.2.11, 3.3.8, 3.4.4. Exact commands for each OS are on this page.

Is CVE-2024-6107 being exploited?

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

CVE-2024-6107 affects metal as a service. Severity is critical (CVSS 9.6). Due to insufficient verification, an attacker could use a malicious client to bypass authentication checks and run RPC commands in a region. This has been addressed in MAAS and updated in the corresponding snaps.

How urgent is CVE-2024-6107?

Priority 48/100. Critical severity; Public exploit reference

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.