How severe is CVE-2024-8038?

CVE-2024-8038 has a CVSS score of 7.9/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-8038?

CVE-2024-8038 affects the following packages: github.com/juju/juju (Go). Ecosystems affected: Go.

How do I fix CVE-2024-8038?

Update github.com/juju/juju to 0.0.0-20240829052008-43f0fc59790d or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-8038 is resolved across your whole dependency graph.

How do I detect CVE-2024-8038 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/juju/juju, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-8038 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2024-8038 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-8038 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-8038?

CVE-2024-8038 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 12th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-8038?

CVE-2024-8038 is classified as CWE-420 (CWE-420). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-8038 published, and has it been updated?

CVE-2024-8038 was published on October 2, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2024-8038 — juju

HIGHFix: juju/juju@43f0fc5

CVE-2024-8038 is a high-severity (CVSS 7.9) CWE-420 vulnerability in github.com/juju/juju. A fix is available for github.com/juju/juju — see the affected versions and patch details below.

Vulnerable juju introspection abstract UNIX domain socket

Also known asGHSA-xwgj-vpm9-q2rqGO-2024-3175

Published

Oct 2, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-8038.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/juju/juju

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

An abstract UNIX domain socket responsible for introspection is available without authentication locally to any user with access to the network namespace where the local juju agent is running.

On a juju controller agent, denial of service can be performed by using the /leases/revoke endpoint. Revoking leases in juju can cause availability issues.

On a juju machine agent that is hosting units, disabling the unit component can be performed using the /units endpoint with a "stop" action.

Patches

Patch: https://github.com/juju/juju/commit/43f0fc59790d220a457d4d305f484f62be556d3b Patched in:

3.5.4
3.4.6
3.3.7
3.1.10
2.9.51

Workarounds

No workaround.

References

https://github.com/juju/juju/blob/725800953aaa29dbeda4f806097bf838e61644dd/worker/introspection/worker.go#L125

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/juju/juju`	all versions	0.0.0-20240829052008-43f0fc59790d`go get github.com/juju/juju@v0.0.0-20240829052008-43f0fc59790d`

Affected Products

1 product · 6 configurations

Application

jujucanonical

≥ 3.5.0 && ≤ 3.2.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/juju/juju, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/juju/juju to 0.0.0-20240829052008-43f0fc59790d or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-8038 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact An abstract UNIX domain socket responsible for introspection is available without authentication locally to any user with access to the network namespace where the local juju agent is running. On a juju controller agent, denial of service can be performed by using the `/leases/revoke` endpoint. Revoking leases in juju can cause availability issues. On a juju machine agent that is hosting units, disabling the unit component can be performed using the `/units` endpoint with a "stop" action. ### Patches Patch: https://github.com/juju/juju/commit/43f0fc59790d220a457d4d305f484f62be556