<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 09 Oct 2026 13:47:39 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-336155</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-336155</link>
      <description>EUVD-2026-336155</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-336155</guid>
    </item>
    <item>
      <title>fkie_cve-2026-55882</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-55882</link>
      <description>&lt;p&gt;Tilt defines dev environments as code for microservice apps on Kubernetes. From 0.19.5 through 0.37.3, the Tilt HUD server mounts Go net/http/pprof handlers under /debug with no access control. When the HUD or apiserver listener is network-exposed, an unauthenticated caller can read process memory through /debug/pprof/heap and /debug/pprof/goroutine, including session and apiserver tokens, and degrade performance through /debug/pprof/profile or /debug/pprof/trace. This issue is fixed in version 0.37.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Tilt defines dev environments as code for microservice apps on Kubernetes. From 0.19.5 through 0.37.3, the Tilt HUD server mounts Go net/http/pprof handlers under /debug with no access control. When the HUD or apiserver listener is network-exposed, an unauthenticated caller can read process memory through /debug/pprof/heap and /debug/pprof/goroutine, including session and apiserver tokens, and degrade performance through /debug/pprof/profile or /debug/pprof/trace. This issue is fixed in version 0.37.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-55882</guid>
    </item>
    <item>
      <title>GHSA-p749-9w62-w533 — Tilt: Unauthenticated pprof debug endpoints on the Tilt HUD server</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p749-9w62-w533</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/tilt-dev/tilt&lt;/p&gt;
&lt;p&gt;## Summary
The Tilt HUD server mounts Go&amp;#39;s `net/http/pprof` handlers under `/debug` with no access control. When the HUD is network-exposed, an attacker can read process memory — including session and apiserver tokens — and hold the process under profiling.&lt;/p&gt;
&lt;p&gt;## Details
A blank import of `net/http/pprof` registers its handlers on `http.DefaultServeMux`, which the HUD controller mounts under `/debug` on both the web router and the apiserver listener. `/debug/pprof/heap` and `/goroutine` expose process memory, including the session token (also issued in the `Tilt-Token` cookie) and the apiserver loopback bearer token; `/profile` and `/trace` let a caller sample the process for an arbitrary duration.&lt;/p&gt;
&lt;p&gt;## Impact
An unauthenticated caller who can reach the listener can extract process memory — including the session and apiserver tokens — and degrade performance by holding the process under CPU profiling or tracing. The leaked tokens compound the missing-authentication finding on the same server.&lt;/p&gt;
&lt;p&gt;### Conditions for exploitation
- Affected version in `&amp;gt;= 0.19.5, &amp;lt;= 0.37.3`.
- HUD (or apiserver) listener bound to a non-loopback address (`tilt up --host 0.0.0.0`, or `TILT_HOST` set).
- Network reachability to the listener (default port `10350`).&lt;/p&gt;
&lt;p&gt;### Not affected
- The default loopback-only bind is not reachable from the network.&lt;/p&gt;
&lt;p&gt;## Workarounds
Use the default loopback bind (omit `--host`, unset `TILT_HOST`) so `/debug` is not remotely reachable. No complete workaround short of upgr…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/tilt-dev/tilt&lt;/p&gt;
&lt;p&gt;## Summary
The Tilt HUD server mounts Go&amp;#39;s `net/http/pprof` handlers under `/debug` with no access control. When the HUD is network-exposed, an attacker can read process memory — including session and apiserver tokens — and hold the process under profiling.&lt;/p&gt;
&lt;p&gt;## Details
A blank import of `net/http/pprof` registers its handlers on `http.DefaultServeMux`, which the HUD controller mounts under `/debug` on both the web router and the apiserver listener. `/debug/pprof/heap` and `/goroutine` expose process memory, including the session token (also issued in the `Tilt-Token` cookie) and the apiserver loopback bearer token; `/profile` and `/trace` let a caller sample the process for an arbitrary duration.&lt;/p&gt;
&lt;p&gt;## Impact
An unauthenticated caller who can reach the listener can extract process memory — including the session and apiserver tokens — and degrade performance by holding the process under CPU profiling or tracing. The leaked tokens compound the missing-authentication finding on the same server.&lt;/p&gt;
&lt;p&gt;### Conditions for exploitation
- Affected version in `&amp;gt;= 0.19.5, &amp;lt;= 0.37.3`.
- HUD (or apiserver) listener bound to a non-loopback address (`tilt up --host 0.0.0.0`, or `TILT_HOST` set).
- Network reachability to the listener (default port `10350`).&lt;/p&gt;
&lt;p&gt;### Not affected
- The default loopback-only bind is not reachable from the network.&lt;/p&gt;
&lt;p&gt;## Workarounds
Use the default loopback bind (omit `--host`, unset `TILT_HOST`) so `/debug` is not remotely reachable. No complete workaround short of upgr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p749-9w62-w533</guid>
    </item>
  </channel>
</rss>
