<?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>Wed, 18 Nov 2026 07:02:18 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-407488</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-407488</link>
      <description>EUVD-2026-407488</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-407488</guid>
    </item>
    <item>
      <title>fkie_cve-2026-130622</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-130622</link>
      <description>&lt;p&gt;Incorrect authorization in the credential loading logic in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before 1.12.0 might allow an authenticated remote user with permission to create namespace-scoped issuers to obtain certificates, including subordinate CA certificates, signed by another namespace&amp;#39;s AWS Private CA with that namespace&amp;#39;s stored AWS credentials, via a namespace-scoped issuer that references a credentials Secret in that namespace.&lt;/p&gt;
&lt;p&gt;To remediate this issue, users should first copy any credentials Secret they intend a namespace-scoped issuer to use into that issuer&amp;#39;s namespace and update the issuer&amp;#39;s secretRef.namespace to match. Then, upgrade aws-privateca-issuer to version 1.12.0 or the AWS Private CA Connector for Kubernetes EKS add-on to version v1.12.0-eksbuild.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Incorrect authorization in the credential loading logic in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before 1.12.0 might allow an authenticated remote user with permission to create namespace-scoped issuers to obtain certificates, including subordinate CA certificates, signed by another namespace&amp;#39;s AWS Private CA with that namespace&amp;#39;s stored AWS credentials, via a namespace-scoped issuer that references a credentials Secret in that namespace.&lt;/p&gt;
&lt;p&gt;To remediate this issue, users should first copy any credentials Secret they intend a namespace-scoped issuer to use into that issuer&amp;#39;s namespace and update the issuer&amp;#39;s secretRef.namespace to match. Then, upgrade aws-privateca-issuer to version 1.12.0 or the AWS Private CA Connector for Kubernetes EKS add-on to version v1.12.0-eksbuild.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-130622</guid>
    </item>
  </channel>
</rss>
