<?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://vulnerability.circl.lu</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, 29 Sep 2026 20:35:05 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-59341</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-59341</link>
      <description>&lt;p&gt;A security vulnerability exists in the Sealed Secrets controller&amp;#39;s unauthenticated POST endpoints. By submitting a modified payload containing custom Go template logic in spec.template.data, an attacker with internal network access can abuse the handler as a decryption oracle to recover the full plaintext of any sealed secret.&lt;/p&gt;
&lt;p&gt;The POST /v1/verify and /v1/rotate handlers call Unseal() to decrypt target secrets, then render any Go templates found in spec.template.data.* using the decrypted payload as the evaluation context (pkg/apis/sealedsecrets/v1alpha1/sealedsecret_expansion.go). Errors encountered during template execution are directly reflected in the resulting HTTP response status codes.&lt;/p&gt;
&lt;p&gt;Missing AEAD label binding: the spec.template.data field is omitted from the AEAD authenticated-data label binding ciphertext to metadata. As a result, an attacker can copy a target&amp;#39;s valid metadata and encryptedData verbatim, satisfying AEAD decryption and label validation, while freely replacing spec.template.data with arbitrary template logic.&lt;/p&gt;
&lt;p&gt;Side-channel oracle: template execution errors map directly to HTTP response codes. HTTP 200 (OK) indicates template execution succeeded; HTTP 409 (Conflict) indicates template execution failed (e.g. via {{ fail &amp;#34;...&amp;#34; }}).&lt;/p&gt;
&lt;p&gt;By injecting conditional statements such as {{ if eq (substr 0 1 .password) &amp;#34;S&amp;#34; }}ok{{ else }}{{ fail &amp;#34;x&amp;#34; }}{{ end }}, an attacker receives an HTTP 200 status when a character guess is correct and an HTTP 409 when…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A security vulnerability exists in the Sealed Secrets controller&amp;#39;s unauthenticated POST endpoints. By submitting a modified payload containing custom Go template logic in spec.template.data, an attacker with internal network access can abuse the handler as a decryption oracle to recover the full plaintext of any sealed secret.&lt;/p&gt;
&lt;p&gt;The POST /v1/verify and /v1/rotate handlers call Unseal() to decrypt target secrets, then render any Go templates found in spec.template.data.* using the decrypted payload as the evaluation context (pkg/apis/sealedsecrets/v1alpha1/sealedsecret_expansion.go). Errors encountered during template execution are directly reflected in the resulting HTTP response status codes.&lt;/p&gt;
&lt;p&gt;Missing AEAD label binding: the spec.template.data field is omitted from the AEAD authenticated-data label binding ciphertext to metadata. As a result, an attacker can copy a target&amp;#39;s valid metadata and encryptedData verbatim, satisfying AEAD decryption and label validation, while freely replacing spec.template.data with arbitrary template logic.&lt;/p&gt;
&lt;p&gt;Side-channel oracle: template execution errors map directly to HTTP response codes. HTTP 200 (OK) indicates template execution succeeded; HTTP 409 (Conflict) indicates template execution failed (e.g. via {{ fail &amp;#34;...&amp;#34; }}).&lt;/p&gt;
&lt;p&gt;By injecting conditional statements such as {{ if eq (substr 0 1 .password) &amp;#34;S&amp;#34; }}ok{{ else }}{{ fail &amp;#34;x&amp;#34; }}{{ end }}, an attacker receives an HTTP 200 status when a character guess is correct and an HTTP 409 when…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-59341</guid>
    </item>
  </channel>
</rss>
