<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T14:20:24.606611+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2025-4673</id>
    <title>CVE-2025-4673 — Sensitive headers not cleared on cross-origin redirect in net/http</title>
    <updated>2026-10-08T14:20:24.609686+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go standard library net/http</p>
<p>Proxy-Authorization and Proxy-Authenticate headers persisted on cross-origin redirects potentially leaking sensitive information.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-4673"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9h84-qmv7-982p</id>
    <title>GHSA-9h84-qmv7-982p — Helm Charts with Specific JSON Schema Values Can Cause Memory Exhaustion</title>
    <updated>2026-10-08T14:20:24.609738+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: helm.sh/helm/v3</p>
<p>A Helm contributor discovered that it was possible to craft a JSON Schema file in a manner which could cause Helm to use all available memory and have an out of memory (OOM) termination.</p>
<p>### Impact
A malicious chart can point `$ref` in _values.schema.json_ to a device (e.g. `/dev/*`) or other problem file which could cause Helm to use all available memory and have an out of memory (OOM) termination.</p>
<p>### Patches
This issue has been resolved in Helm v3.18.5.</p>
<p>### Workarounds
Make sure that all Helm charts that are being loaded into Helm doesn't have any reference of `$ref` pointing to `/dev/zero`.</p>
<p>### References
Helm's security policy is spelled out in detail in our [SECURITY](https://github.com/helm/community/blob/master/SECURITY.md) document.</p>
<p>### Credits
Disclosed by Jakub Ciolek at AlphaSense.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9h84-qmv7-982p"/>
  </entry>
</feed>
