Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Helm contains Denial of service through schema file

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2022-23526

Published

Helm is a tool for managing Charts, pre-configured Kubernetes resources. Versions prior to 3.10.3 are subject to NULL Pointer Dereference in the_chartutil_ package that can cause a segmentation violation. The _chartutil_ package contains a parser that loads a JSON Schema validation file. For example, the Helm client when rendering a chart will validate its values with the schema file. The _chartutil_ package parses the schema file and loads it into structures Go can work with. Some schema files can cause array data structures to be created causing a memory violation. Applications that use the _chartutil_ package in the Helm SDK to parse a schema file can suffer a Denial of Service when that input causes a panic that cannot be recovered from. Helm is not a long running service so the panic will not affect future uses of the Helm client. This issue has been patched in 3.10.3. SDK users can validate schema files that are correctly formatted before passing them to the _chartutil_ functions.

Source published
15 Dec 2022 00:43:40 UTC
Source modified
18 Apr 2025 15:58:33 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

euvd · EUVD-2022-7524

Published

Helm is a tool for managing Charts, pre-configured Kubernetes resources. Versions prior to 3.10.3 are subject to NULL Pointer Dereference in the_chartutil_ package that can cause a segmentation violation. The _chartutil_ package contains a parser that loads a JSON Schema validation file. For example, the Helm client when rendering a chart will validate its values with the schema file. The _chartutil_ package parses the schema file and loads it into structures Go can work with. Some schema files can cause array data structures to be created causing a memory violation. Applications that use the _chartutil_ package in the Helm SDK to parse a schema file can suffer a Denial of Service when that input causes a panic that cannot be recovered from. Helm is not a long running service so the panic will not affect future uses of the Helm client. This issue has been patched in 3.10.3. SDK users can validate schema files that are correctly formatted before passing them to the _chartutil_ functions.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Dec 15, 2022, 12:43:40 AM

dateUpdated: Apr 18, 2025, 3:58:33 PM

9 related source bulletins · separate from aliases

SUSE-SU-2022:4606-1: Security update for helm

CVE-2021-21272 · CVE-2022-1996 · CVE-2022-23524 · CVE-2022-23525 · CVE-2022-23526

msrc_CVE-2022-23526: Helm contains Denial of service through schema file

CVE-2022-23526

RHSA-2023:1326: Red Hat Security Advisory: OpenShift Container Platform 4.13.0 security update

CVE-2021-4235 · CVE-2021-4238 · CVE-2021-20329 · CVE-2021-38561 · CVE-2022-21698 · CVE-2022-23525 · CVE-2022-23526 · CVE-2022-27191 · CVE-2022-41316 · CVE-2022-41717 · CVE-2022-41721 · CVE-2022-41723 · CVE-2022-41724 · CVE-2022-41725 · CVE-2022-46146 · CVE-2023-0620 · CVE-2023-0665 · CVE-2023-25000 · CVE-2023-25165 · CVE-2023-25173 · CVE-2023-25809 · CVE-2023-27561 · CVE-2023-28642 · CVE-2023-30841

openSUSE-SU-2025:15779-1: helm3-3.19.2-1.1 on GA media

CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2021-21272 · CVE-2022-1996 · CVE-2022-23524 · CVE-2022-23525 · CVE-2022-23526 · CVE-2022-36055 · CVE-2023-25165 · CVE-2023-25173 · CVE-2024-25620 · CVE-2024-26147 · CVE-2024-45337 · CVE-2024-45338 · CVE-2025-22870 · CVE-2025-22872 · CVE-2025-47911 · CVE-2025-53547 · CVE-2025-58190

openSUSE-SU-2024:12572-1: helm-3.10.3-2.1 on GA media

CVE-2022-23524 · CVE-2022-23525 · CVE-2022-23526

RHSA-2023:1646: Red Hat Security Advisory: OpenShift Container Platform 4.12.11 security update

CVE-2022-23524 · CVE-2022-23525 · CVE-2022-23526

RHSA-2023:5006: Red Hat Security Advisory: OpenShift Container Platform 4.14.0 bug fix and security update

CVE-2018-17419 · CVE-2021-4294 · CVE-2021-20329 · CVE-2021-36157 · CVE-2022-3064 · CVE-2022-23525 · CVE-2022-23526 · CVE-2022-41723 · CVE-2023-0475 · CVE-2023-0620 · CVE-2023-0665 · CVE-2023-3089 · CVE-2023-3978 · CVE-2023-5408 · CVE-2023-25000 · CVE-2023-25165 · CVE-2023-25173 · CVE-2023-26115 · CVE-2023-26136 · CVE-2023-27561 · CVE-2023-29401 · CVE-2023-37788 · CVE-2023-39325 · CVE-2023-44487

WID-SEC-W-2023-0912: Red Hat OpenShift: Mehrere Schwachstellen ermöglichen Denial of Service

CVE-2022-23526 · CVE-2022-23525 · CVE-2022-23524

WID-SEC-W-2024-1591: Juniper JUNOS: Mehrere Schwachstellen

CVE-2006-20001 · CVE-2007-5846 · CVE-2008-6123 · CVE-2011-1473 · CVE-2011-5094 · CVE-2012-6151 · CVE-2014-10064 · CVE-2014-2285 · CVE-2014-2310 · CVE-2014-3565 · CVE-2014-7191 · CVE-2014-8882 · CVE-2015-5621 · CVE-2015-8100 · CVE-2015-9262 · CVE-2016-1000232 · CVE-2016-10540 · CVE-2016-4658 · CVE-2017-1000048 · CVE-2017-15010 · CVE-2018-18065 · CVE-2018-20834 · CVE-2018-3737 · CVE-2018-7408 · CVE-2019-10081 · CVE-2019-10082 · CVE-2019-10092 · CVE-2019-10097 · CVE-2019-10098 · CVE-2019-11719 · CVE-2019-11727 · CVE-2019-11756 · CVE-2019-16775 · CVE-2019-16776 · CVE-2019-16777 · CVE-2019-17006 · CVE-2019-17023 · CVE-2019-17567 · CVE-2019-20149 · CVE-2019-20892 · CVE-2019-9517 · CVE-2020-11668 · CVE-2020-11984 · CVE-2020-11993 · CVE-2020-12362 · CVE-2020-12400 · CVE-2020-12401 · CVE-2020-12402 · CVE-2020-12403 · CVE-2020-13938 · CVE-2020-13950 · CVE-2020-14145 · CVE-2020-15861 · CVE-2020-15862 · CVE-2020-1927 · CVE-2020-1934 · CVE-2020-28469 · CVE-2020-28502 · CVE-2020-35452 · CVE-2020-36049 · CVE-2020-6829 · CVE-2020-7660 · CVE-2020-7754 · CVE-2020-7774 · CVE-2020-8648 · CVE-2020-9490 · CVE-2021-22543 · CVE-2021-2342 · CVE-2021-23440 · CVE-2021-2356 · CVE-2021-2372 · CVE-2021-2385 · CVE-2021-2389 · CVE-2021-2390 · CVE-2021-25745 · CVE-2021-25746 · CVE-2021-25748 · CVE-2021-26690 · CVE-2021-26691 · CVE-2021-27290 · CVE-2021-29469 · CVE-2021-30641 · CVE-2021-31535 · CVE-2021-31618 · CVE-2021-3177 · CVE-2021-32803 · CVE-2021-32804 · CVE-2021-33033 · CVE-2021-33034 · CVE-2021-33193 · CVE-2021-3347 · CVE-2021-33909 · CVE-2021-34798 · CVE-2021-35604 · CVE-2021-35624 · CVE-2021-36160 · CVE-2021-37701 · CVE-2021-37712 · CVE-2021-37713 · CVE-2021-3803 · CVE-2021-39275 · CVE-2021-40438 · CVE-2021-41524 · CVE-2021-41773 · CVE-2021-42013 · CVE-2021-43527 · CVE-2021-44224 · CVE-2021-44225 · CVE-2021-44790 · CVE-2021-44906 · CVE-2022-21245 · CVE-2022-21270 · CVE-2022-21303 · CVE-2022-21304 · CVE-2022-21344 · CVE-2022-21367 · CVE-2022-21417 · CVE-2022-21427 · CVE-2022-21444 · CVE-2022-21451 · CVE-2022-21454 · CVE-2022-21460 · CVE-2022-21589 · CVE-2022-21592 · CVE-2022-21595 · CVE-2022-21608 · CVE-2022-21617 · CVE-2022-22719 · CVE-2022-22720 · CVE-2022-22721 · CVE-2022-22822 · CVE-2022-22823 · CVE-2022-22824 · CVE-2022-23471 · CVE-2022-23524 · CVE-2022-23525 · CVE-2022-23526 · CVE-2022-23852 · CVE-2022-23943 · CVE-2022-25147 · CVE-2022-25235 · CVE-2022-25236 · CVE-2022-2526 · CVE-2022-25315 · CVE-2022-26377 · CVE-2022-28330 · CVE-2022-28614 · CVE-2022-28615 · CVE-2022-29167 · CVE-2022-29404 · CVE-2022-30522 · CVE-2022-30556 · CVE-2022-31813 · CVE-2022-3517 · CVE-2022-3564 · CVE-2022-36760 · CVE-2022-37434 · CVE-2022-37436 · CVE-2022-40674 · CVE-2022-41741 · CVE-2022-41742 · CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2022-46663 · CVE-2022-4886 · CVE-2023-0215 · CVE-2023-0216 · CVE-2023-0217 · CVE-2023-0286 · CVE-2023-0401 · CVE-2023-0464 · CVE-2023-0465 · CVE-2023-0466 · CVE-2023-0767 · CVE-2023-1255 · CVE-2023-2002 · CVE-2023-20593 · CVE-2023-21830 · CVE-2023-21840 · CVE-2023-21843 · CVE-2023-21912 · CVE-2023-21963 · CVE-2023-21980 · CVE-2023-22025 · CVE-2023-22067 · CVE-2023-22081 · CVE-2023-22652 · CVE-2023-24329 · CVE-2023-25153 · CVE-2023-25173 · CVE-2023-25690 · CVE-2023-2700 · CVE-2023-27522 · CVE-2023-2828 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2023-2975 · CVE-2023-30079 · CVE-2023-30630 · CVE-2023-3090 · CVE-2023-32067 · CVE-2023-32360 · CVE-2023-32435 · CVE-2023-32439 · CVE-2023-32732 · CVE-2023-3341 · CVE-2023-3390 · CVE-2023-33953 · CVE-2023-34058 · CVE-2023-34059 · CVE-2023-3446 · CVE-2023-34969 · CVE-2023-35001 · CVE-2023-35788 · CVE-2023-3611 · CVE-2023-37450 · CVE-2023-3776 · CVE-2023-3817 · CVE-2023-4004 · CVE-2023-4206 · CVE-2023-4207 · CVE-2023-4208 · CVE-2023-42753 · CVE-2023-4785 · CVE-2023-4807 · CVE-2023-4863 · CVE-2023-5043 · CVE-2023-5129 · CVE-2023-5363 · CVE-2024-20918 · CVE-2024-20919 · CVE-2024-20921 · CVE-2024-20926 · CVE-2024-20932 · CVE-2024-20945 · CVE-2024-20952 · CVE-2024-39511 · CVE-2024-39512 · CVE-2024-39513 · CVE-2024-39514 · CVE-2024-39517 · CVE-2024-39518 · CVE-2024-39519 · CVE-2024-39520 · CVE-2024-39521 · CVE-2024-39522 · CVE-2024-39523 · CVE-2024-39524 · CVE-2024-39528 · CVE-2024-39529 · CVE-2024-39530 · CVE-2024-39531 · CVE-2024-39532 · CVE-2024-39533 · CVE-2024-39535 · CVE-2024-39536 · CVE-2024-39537 · CVE-2024-39538 · CVE-2024-39539 · CVE-2024-39540 · CVE-2024-39541 · CVE-2024-39542 · CVE-2024-39543 · CVE-2024-39545 · CVE-2024-39546 · CVE-2024-39548 · CVE-2024-39549 · CVE-2024-39550 · CVE-2024-39551 · CVE-2024-39553 · CVE-2024-39554 · CVE-2024-39555 · CVE-2024-39556 · CVE-2024-39557 · CVE-2024-39558 · CVE-2024-39559 · CVE-2024-39560 · CVE-2024-39561 · CVE-2024-39565

Source published
Dec 15, 2022, 12:43:40 AM (timezone not stated)
Source modified
Apr 18, 2025, 3:58:33 PM (timezone not stated)
Saved here
18 Nov 2026 03:38:54 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

nvd · CVE-2022-23526

Published

Helm is a tool for managing Charts, pre-configured Kubernetes resources. Versions prior to 3.10.3 are subject to NULL Pointer Dereference in the_chartutil_ package that can cause a segmentation violation. The _chartutil_ package contains a parser that loads a JSON Schema validation file. For example, the Helm client when rendering a chart will validate its values with the schema file. The _chartutil_ package parses the schema file and loads it into structures Go can work with. Some schema files can cause array data structures to be created causing a memory violation. Applications that use the _chartutil_ package in the Helm SDK to parse a schema file can suffer a Denial of Service when that input causes a panic that cannot be recovered from. Helm is not a long running service so the panic will not affect future uses of the Helm client. This issue has been patched in 3.10.3. SDK users can validate schema files that are correctly formatted before passing them to the _chartutil_ functions.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-476

Original publisher date fields

published: 2022-12-15T19:15:17.167

lastModified: 2026-06-17T04:30:18.020

1 source CPE criteria · context only
  • cpe:2.3:a:helm:helm:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
15 Dec 2022 19:15:17 UTC
Source modified
17 Jun 2026 04:30:18 UTC
Saved here
24 Oct 2026 19:17:49 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CVSS 3.1 · [email protected] · Primary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

osv · GHSA-67fx-wx78-jx33

Published

Fuzz testing, by Ada Logics and sponsored by the CNCF, identified input to functions in the `_chartutil_` package that can cause a segmentation violation. Applications that use functions from the `_chartutil_` package in the Helm SDK can have a Denial of Service attack when they use this package and it panics. ### Impact The `_chartutil_` package contains a parser that loads a JSON Schema validation file. For example, the Helm client when rendering a chart will validate its values with the schema file. The `_chartutil_` package parses the schema file and loads it into structures Go can work with. Some schema files can cause array data structures to be created causing a memory violation. Applications that use the `_chartutil_` package in the Helm SDK to parse a schema file can suffer a Denial of Service when that input causes a panic that cannot be recovered from. The Helm Client will panic with a schema file that causes a memory violation panic. Helm is not a long running service so the panic will not affect future uses of the Helm client. ### Patches This issue has been resolved in 3.10.3. ### Workarounds SDK users can validate schema files that are correctly formatted before passing them to the `_chartutil_` functions. ### For more information Helm's security policy is spelled out in detail in our [SECURITY](https://github.com/helm/community/blob/master/SECURITY.md) document. ### Credits Disclosed by Ada Logics in a fuzzing audit sponsored by CNCF.

Source published
14 Dec 2022 21:39:06 UTC
Source modified
10 Sep 2026 03:49:47 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

Publisher rating · MODERATE

osv · GO-2022-1166

Published

Certain JSON schema validation files can cause a Helm Client to panic, leading to a possible denial of service. The chartutil package contains a parser that loads a JSON Schema validation file. For example, the Helm client when rendering a chart will validate its values with the schema file. The chartutil package parses the schema file and loads it into memory, but some schema files can cause array data structures to be created causing a memory violation. The Helm Client will panic with a schema file that causes a memory violation panic. Helm is not a long running service so the panic will not affect future uses of the Helm client.

Source published
22 Dec 2022 22:30:45 UTC
Source modified
4 Feb 2026 04:39:30 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 04:49 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current