How severe is CVE-2025-24884?

No CVSS score has been assigned to CVE-2025-24884 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-24884?

CVE-2025-24884 affects the following packages: github.com/RichardoC/kube-audit-rest (Go). Ecosystems affected: Go.

How do I fix CVE-2025-24884?

Update github.com/RichardoC/kube-audit-rest to 0.0.0-20250205113217-9df8886b4819 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-24884 is resolved across your whole dependency graph.

How do I detect CVE-2025-24884 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/RichardoC/kube-audit-rest. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-24884?

O3 pinpoints whether CVE-2025-24884 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2025-24884 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-24884 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 type of vulnerability is CVE-2025-24884?

CVE-2025-24884 is classified as Information Exposure (CWE-200), CWE-212 (CWE-212), CWE-532 (CWE-532). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-24884 published, and has it been updated?

CVE-2025-24884 was published on January 29, 2025 and was last updated on August 8, 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

CVE-2025-24884

Fix: RichardoC/kube-audit-rest@db1aa5b

CVE-2025-24884 is a Information Exposure vulnerability in github.com/RichardoC/kube-audit-rest. O3 Security confirms whether CVE-2025-24884 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

kube-audit-rest's example logging configuration could disclose secret values in the audit log

Also known asGHSA-hcr5-wv4p-h2g2GO-2025-3431

Published

Jan 29, 2025

Updated

Aug 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐹github.com/RichardoC/kube-audit-rest

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

kube-audit-rest is a simple logger of mutation/creation requests to the k8s api. If the "full-elastic-stack" example vector configuration was used for a real cluster, the previous values of kubernetes secrets would have been disclosed in the audit messages. This vulnerability is fixed in 1.0.16.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/RichardoC/kube-audit-rest`	all versions	0.0.0-20250205113217-9df8886b4819

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/RichardoC/kube-audit-rest. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/RichardoC/kube-audit-rest to 0.0.0-20250205113217-9df8886b4819 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-24884 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-24884 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-24884. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-24884 in your dependencies?

O3 detects CVE-2025-24884 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works