NVD / CVE Program· CNA canonical

CVE-2024-6174: When a non-x86 platform is detected, cloud-init grants root access to a hardcoded url with a local IP address.

Noroxi assessment

Priority: Monitor (action score 35/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Canonical cloud-init 25.1.3.

Low priority for now. Upgrade to Canonical cloud-init 25.1.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

When a non-x86 platform is detected, cloud-init grants root access to a hardcoded url with a local IP address. To prevent this, cloud-init default configurations disable platform enumeration.

HighCVSS 8.8 · v3.1—No exploit Fix available

Published: Jun 26, 2025
Updated: Jun 17, 2026
EPSS: 0.2% · 18th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · canonical: 8.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
canonical	cloud-init	cpe:2.3:a:canonical:cloud-init

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

canonical cloud-initbefore 25.1.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (canonical). Independent of NVD's CPE analysis and usually ahead of it.

Canonical cloud-init
- 0.7.9 and later · before 25.1.3affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:10	cloud-init	before 24.4-3.el10_0.2	24.4-3.el10_0.2
AlmaLinux:8	cloud-init	before 23.4-7.el8_10.10.alma.1	23.4-7.el8_10.10.alma.1
AlmaLinux:9	cloud-init	before 24.4-4.el9_6.3.alma.1	24.4-4.el9_6.3.alma.1
Debian:12	cloud-init	before 22.4.2-1+deb12u3	22.4.2-1+deb12u3
Debian:13	cloud-init	before 25.1.4-1	25.1.4-1
openSUSE:Leap 16.0	cloud-init	before 25.1.3-160000.2.1	25.1.3-160000.2.1
openSUSE:Tumbleweed	cloud-init	before 25.1.3-1.1	25.1.3-1.1
Red Hat:enterprise_linux:10.0	cloud-init	before 0:24.4-3.el10_0.2	0:24.4-3.el10_0.2
Red Hat:enterprise_linux:8::appstream	cloud-init	before 0:23.4-7.el8_10.10	0:23.4-7.el8_10.10
Red Hat:enterprise_linux:9::appstream	cloud-init	before 0:24.4-4.el9_6.3	0:24.4-4.el9_6.3
Red Hat:rhel_aus:8.6::appstream	cloud-init	before 0:21.1-15.el8_6.4	0:21.1-15.el8_6.4
Red Hat:rhel_e4s:8.8::appstream	cloud-init	before 0:22.1-8.el8_8.2	0:22.1-8.el8_8.2
Red Hat:rhel_e4s:9.0::appstream	cloud-init	before 0:21.1-19.el9_0.7	0:21.1-19.el9_0.7
Red Hat:rhel_e4s:9.2::appstream	cloud-init	before 0:22.1-10.el9_2.1	0:22.1-10.el9_2.1
Red Hat:rhel_eus:9.4::appstream	cloud-init	before 0:23.4-7.el9_4.13	0:23.4-7.el9_4.13
Rocky Linux:8	cloud-init	before 0:23.4-7.el8_10.10.0.2	0:23.4-7.el8_10.10.0.2
SUSE:Linux Micro 6.0	cloud-init	before 25.1.3-1.1	25.1.3-1.1
SUSE:Linux Micro 6.1	cloud-init	before 25.1.3-slfo.1.1_1.1	25.1.3-slfo.1.1_1.1
SUSE:Linux Micro 6.2	cloud-init	before 25.1.3-160000.2.1	25.1.3-160000.2.1

Same product

canonical: all records

Other highest-scoring records for the same primary product.

CVE-2012-6639An privilege elevation vulnerability exists in Cloud-init before 0.7.0 when requests to an untrusted system are submitted for EC2 instance d
36Monitor
CVE-2018-10896The default cloud-init configuration, in cloud-init 0.6.2 and newer, included "ssh_deletekeys: 0", disabling cloud-init's deletion of ssh ho
28Monitor
CVE-2023-1786sensitive data exposure in cloud-init logs
22Monitor

Published before and after this one in the same product

← EarlierCVE-2021-3429Apr 19, 2023 · sensitive data exposure in cloud-init logs
22Monitor
← EarlierCVE-2022-2084Apr 19, 2023 · sensitive data exposure in cloud-init logs
22Monitor
← EarlierCVE-2024-11584Jun 26, 2025 · cloud-init through 25.1.2 includes the systemd socket unit cloud-init-hotplugd.socket with default SocketMode that grants 0666 permissions,
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Canonical cloud-init	25.1.3	Vendor (CNA)
almalinux:cloud-init	24.4-3.el10_0.2 · AlmaLinux:10	Package registry (OSV)
debian:cloud-init	22.4.2-1+deb12u3 · Debian:12	Package registry (OSV)
opensuse:cloud-init	25.1.3-160000.2.1 · openSUSE:Leap 16.0	Package registry (OSV)
red hat:cloud-init	0:24.4-3.el10_0.2 · Red Hat:enterprise_linux:10.0	Package registry (OSV)
rocky linux:cloud-init	0:23.4-7.el8_10.10.0.2 · Rocky Linux:8	Package registry (OSV)
suse:cloud-init	25.1.3-160000.2.1 · SUSE:Linux Micro 6.2	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone on the same network segment can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Adjacent
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/canonical/cloud-init/releases/tag/25.1.3

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records