CVE-2019-25210

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2024-03-03. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An issue was discovered in Cloud Native Computing Foundation (CNCF) Helm through 3.13.3. It displays values of secrets when the --dry-run flag is used. This is a security concern in some use cases, such as a --dry-run call by a CI/CD tool. NOTE: the vendor's position is that this behavior was introduced intentionally, and cannot be removed without breaking backwards compatibility (some users may be relying on these values). Also, it is not the Helm Project's responsibility if a user decides to use --dry-run within a CI/CD environment whose output is visible to unauthorized persons.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 3, 2024

Last Modified

February 11, 2025

References (6)

Vendor Advisories for CVE-2019-25210(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift4/ose-operator-registry-rhel9:v4.18.0-202504151633.p0.gcc44b48.assembly.stream.el92025-04-22redhat
redhatopenshift4/ose-operator-sdk-rhel9:v4.18.0-202502110432.p0.gce80aa9.assembly.stream.el92025-02-25redhat
redhatopenshift4/ose-azure-cluster-api-controllers-rhel9:v4.16.0-202406131906.p0.gface7da.assembly.stream.el92024-06-27redhat
redhatadvanced-cluster-security/rhacs-scanner-v4-rhel8:4.4.0-132024-03-28redhat
redhatadvanced-cluster-security/rhacs-scanner-slim-rhel8:4.3.6-32024-03-27redhat
gohelm.sh/helm/v3—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
helm.sh/helm/v3—
  • 3.0.0 through 3.14.2: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 166 total refreshes for this CVE.

  1. 2026-10-09 22:33 UTCOSV refresh
  2. 2026-10-09 20:03 UTCEPSS rescore
  3. 2026-10-08 16:37 UTCEPSS rescore
  4. 2026-10-07 23:43 UTCEPSS rescore
  5. 2026-10-06 15:12 UTCEPSS rescore
  6. 2026-10-05 17:39 UTCEPSS rescore
  7. 2026-10-04 23:18 UTCEPSS rescore
  8. 2026-10-03 14:22 UTCEPSS rescore
  9. 2026-09-30 14:59 UTCEPSS rescore
  10. 2026-09-30 10:18 UTCEG score recompute
  11. 2026-09-28 13:46 UTCEPSS rescore
  12. 2026-09-27 13:40 UTCEPSS rescore
  13. 2026-09-26 15:54 UTCEPSS rescore
  14. 2026-09-26 15:54 UTCEPSS rescore
  15. 2026-09-26 00:20 UTCEPSS rescore
  16. 2026-09-24 13:59 UTCEPSS rescore
  17. 2026-09-23 13:43 UTCEPSS rescore
  18. 2026-09-22 14:43 UTCEPSS rescore
  19. 2026-09-21 20:28 UTCEPSS rescore
  20. 2026-09-20 20:10 UTCEPSS rescore
  21. 2026-09-20 06:43 UTCOSV refresh
  22. 2026-09-18 19:22 UTCEPSS rescore
  23. 2026-09-17 19:22 UTCEPSS rescore
  24. 2026-09-16 14:04 UTCEPSS rescore
  25. 2026-09-15 03:05 UTCEPSS rescore
Show 75 more
  1. 2026-09-13 16:42 UTCEPSS rescore
  2. 2026-09-12 14:56 UTCEPSS rescore
  3. 2026-09-11 14:48 UTCEPSS rescore
  4. 2026-09-11 09:32 UTCEPSS rescore
  5. 2026-09-07 15:57 UTCEPSS rescore
  6. 2026-09-06 13:44 UTCEPSS rescore
  7. 2026-09-05 15:24 UTCEPSS rescore
  8. 2026-09-04 13:56 UTCEPSS rescore
  9. 2026-09-02 14:07 UTCEPSS rescore
  10. 2026-09-01 09:59 UTCOSV refresh
  11. 2026-09-01 03:32 UTCEPSS rescore
  12. 2026-08-30 19:13 UTCEPSS rescore
  13. 2026-08-30 01:18 UTCEPSS rescore
  14. 2026-08-28 21:36 UTCEPSS rescore
  15. 2026-08-27 14:21 UTCEPSS rescore
  16. 2026-08-26 14:42 UTCEPSS rescore
  17. 2026-08-25 13:45 UTCEPSS rescore
  18. 2026-08-24 14:11 UTCEPSS rescore
  19. 2026-08-21 23:45 UTCEPSS rescore
  20. 2026-08-20 22:51 UTCEPSS rescore
  21. 2026-08-19 17:00 UTCEPSS rescore
  22. 2026-08-18 13:44 UTCEPSS rescore
  23. 2026-08-17 13:43 UTCEPSS rescore
  24. 2026-08-16 14:52 UTCEPSS rescore
  25. 2026-08-16 02:10 UTCEPSS rescore
  26. 2026-08-15 09:37 UTCOSV refresh
  27. 2026-08-15 01:26 UTCEPSS rescore
  28. 2026-08-12 13:47 UTCEPSS rescore
  29. 2026-08-09 13:43 UTCEPSS rescore
  30. 2026-08-08 16:33 UTCEPSS rescore
  31. 2026-08-07 16:23 UTCEPSS rescore
  32. 2026-08-06 13:43 UTCEPSS rescore
  33. 2026-08-05 19:13 UTCEPSS rescore
  34. 2026-08-04 15:05 UTCEPSS rescore
  35. 2026-08-02 02:23 UTCEPSS rescore
  36. 2026-08-01 04:12 UTCEPSS rescore
  37. 2026-07-30 21:51 UTCOSV refresh
  38. 2026-07-30 16:24 UTCEPSS rescore
  39. 2026-07-30 01:27 UTCEPSS rescore
  40. 2026-07-28 15:32 UTCEPSS rescore
  41. 2026-07-26 14:51 UTCEPSS rescore
  42. 2026-07-25 14:14 UTCEPSS rescore
  43. 2026-07-24 14:14 UTCEPSS rescore
  44. 2026-07-24 14:14 UTCEPSS rescore
  45. 2026-07-23 14:15 UTCEPSS rescore
  46. 2026-07-23 01:44 UTCEG score recompute
  47. 2026-07-22 22:24 UTCEG score recompute
  48. 2026-07-22 14:05 UTCEPSS rescore
  49. 2026-07-21 15:22 UTCEPSS rescore
  50. 2026-07-21 15:22 UTCEPSS rescore
  51. 2026-07-20 17:04 UTCEPSS rescore
  52. 2026-07-20 17:04 UTCEPSS rescore
  53. 2026-07-19 14:28 UTCEPSS rescore
  54. 2026-07-19 14:28 UTCEPSS rescore
  55. 2026-07-19 02:26 UTCEPSS rescore
  56. 2026-07-19 02:26 UTCEPSS rescore
  57. 2026-07-18 10:01 UTCEPSS rescore
  58. 2026-07-16 16:59 UTCEPSS rescore
  59. 2026-07-16 16:59 UTCEPSS rescore
  60. 2026-07-15 16:55 UTCEPSS rescore
  61. 2026-07-15 16:55 UTCEPSS rescore
  62. 2026-07-13 22:27 UTCEPSS rescore
  63. 2026-07-13 06:38 UTCOSV refresh
  64. 2026-07-13 06:10 UTCEPSS rescore
  65. 2026-07-13 06:10 UTCEPSS rescore
  66. 2026-07-12 05:43 UTCEPSS rescore
  67. 2026-07-12 05:43 UTCEPSS rescore
  68. 2026-07-11 08:24 UTCEPSS rescore
  69. 2026-07-11 08:24 UTCEPSS rescore
  70. 2026-07-09 19:06 UTCEPSS rescore
  71. 2026-07-08 15:11 UTCEPSS rescore
  72. 2026-07-07 13:43 UTCEPSS rescore
  73. 2026-07-06 16:25 UTCEPSS rescore
  74. 2026-07-06 16:25 UTCEPSS rescore
  75. 2026-07-06 02:20 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-25210?
CVE-2019-25210 is a medium vulnerability published on March 3, 2024. An issue was discovered in Cloud Native Computing Foundation (CNCF) Helm through 3.13.3. It displays values of secrets when the --dry-run flag is used. This is a security concern in some use cases, such as a --dry-run call by a CI/CD tool. NOTE: the vendor's position is that this behavior was…
When was CVE-2019-25210 disclosed?
CVE-2019-25210 was first published on March 3, 2024, with the most recent update on February 11, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-25210 actively exploited?
CVE-2019-25210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-25210?
CVE-2019-25210 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2019-25210?
A fix for CVE-2019-25210 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-25210 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-25210

Explore →

Is Your Infrastructure Affected by CVE-2019-25210?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs