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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.1 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X · score source

EPSS

• CVE-2025-24884: 0.19% estimated exploitation activity in the next 30 days; percentile 9.24 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact What kind of vulnerability is it? Who is impacted? 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. Patches Has the problem been patched? What versions should users upgrade to? The example has been updated to fix this in commit 9df8886b4819409f566233adc7c3b7a43a4096ba Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading? Replace In the vector "audit-files-json-parser-and-redaction" step with References Are there any links users can visit to find out more?

Published by the source

29 Jan 2025, 20:47 UTC

Last modified by the source

5 Feb 2025, 16:28 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hcr5-wv4p-h2g2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-24884

Advisory: kube-audit-rest's example logging configuration could disclose secret values in the audit log
IDs: CVE-2025-24884, GHSA-hcr5-wv4p-h2g2
Record: https://patchnext.com/advisories/cve-2025-24884 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/RichardoC/kube-audit-rest 0.0.0-20250205113217-9df8886b4819. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/RichardoC/kube-audit-rest: affected < 0.0.0-20250205113217-9df8886b4819; fixed in 0.0.0-20250205113217-9df8886b4819

## Suggested inspection (read-only)
- Go github.com/RichardoC/kube-audit-rest: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/RichardoC/kube-audit-rest.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hcr5-wv4p-h2g2 (GitHub-reviewed advisory GHSA-hcr5-wv4p-h2g2 lists affected ranges: Go github.com/RichardoC/kube-audit-rest >=0 <0.0.0-20250205113217-9df8886b4819)

Commands are suggestions: review each one before running it.