<?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>Sat, 03 Oct 2026 09:08:21 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: CLEANSTART-2026-AJ39907 — gRPC-Go is the Go language implementation of gRPC</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-aj39907</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: step&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the step package. gRPC-Go is the Go language implementation of gRPC. See references for individual vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: step&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the step package. gRPC-Go is the Go language implementation of gRPC. See references for individual vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-aj39907</guid>
    </item>
    <item>
      <title>EUVD-2026-277397</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-277397</link>
      <description>EUVD-2026-277397</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-277397</guid>
    </item>
    <item>
      <title>fkie_cve-2026-30836</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-30836</link>
      <description>&lt;p&gt;Step CA is an online certificate authority for secure, automated certificate management for DevOps. Versions 0.30.0-rc6 and below do not safeguard against unauthenticated certificate issuance through the SCEP UpdateReq. This issue has been fixed in version 0.30.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Step CA is an online certificate authority for secure, automated certificate management for DevOps. Versions 0.30.0-rc6 and below do not safeguard against unauthenticated certificate issuance through the SCEP UpdateReq. This issue has been fixed in version 0.30.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-30836</guid>
    </item>
    <item>
      <title>GHSA-q4r8-xm5f-56gw — step-ca has Unauthenticated Certificate Issuance via SCEP UpdateReq (MessageType=18)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q4r8-xm5f-56gw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/smallstep/certificates&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;An attacker can force a Step CA SCEP provisioner to create certificates without completing certain protocol authorization checks.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;SCEP requests carry a message type. On receipt of a SCEP request, Step CA starts processing it by parsing its contents. Message types that were considered valid, but not explicitly supported in Step CA, would result in getting parsed successfully. While processing the parsed SCEP message, authorization logic would be skipped for the non-supported message types.&lt;/p&gt;
&lt;p&gt;As a result, the request would be treated as authorized, bypassing the authorization checks normally enforced as part of the SCEP protocol and its implementation in Step CA.&lt;/p&gt;
&lt;p&gt;Authorization webhooks and regular CA policies, such as allowed names and restrictions on certificate validity periods, remain in place.&lt;/p&gt;
&lt;p&gt;## Mitigations&lt;/p&gt;
&lt;p&gt;If you are unable to upgrade to v0.30.0 or newer, the attack can be mitigated by (temporarily) disabling or removing SCEP provisioners, or restricting access to SCEP provisioners to trusted clients only.&lt;/p&gt;
&lt;p&gt;## Fix&lt;/p&gt;
&lt;p&gt;In v0.30.0, additional validation was added to SCEP provisioners, so that they reject unsupported message types.&lt;/p&gt;
&lt;p&gt;## Acknowledgements&lt;/p&gt;
&lt;p&gt;This issue was identified and reported by Prasanth Sundararajan.&lt;/p&gt;
&lt;p&gt;## Embargo List&lt;/p&gt;
&lt;p&gt;If your organization runs Step CA in production and would like advance, embargoed notification of future security updates, visit https://u.step.sm/disclosure to request inclusion on our embargo list.&lt;/p&gt;
&lt;p&gt;Stay safe, and tha…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/smallstep/certificates&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;An attacker can force a Step CA SCEP provisioner to create certificates without completing certain protocol authorization checks.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;SCEP requests carry a message type. On receipt of a SCEP request, Step CA starts processing it by parsing its contents. Message types that were considered valid, but not explicitly supported in Step CA, would result in getting parsed successfully. While processing the parsed SCEP message, authorization logic would be skipped for the non-supported message types.&lt;/p&gt;
&lt;p&gt;As a result, the request would be treated as authorized, bypassing the authorization checks normally enforced as part of the SCEP protocol and its implementation in Step CA.&lt;/p&gt;
&lt;p&gt;Authorization webhooks and regular CA policies, such as allowed names and restrictions on certificate validity periods, remain in place.&lt;/p&gt;
&lt;p&gt;## Mitigations&lt;/p&gt;
&lt;p&gt;If you are unable to upgrade to v0.30.0 or newer, the attack can be mitigated by (temporarily) disabling or removing SCEP provisioners, or restricting access to SCEP provisioners to trusted clients only.&lt;/p&gt;
&lt;p&gt;## Fix&lt;/p&gt;
&lt;p&gt;In v0.30.0, additional validation was added to SCEP provisioners, so that they reject unsupported message types.&lt;/p&gt;
&lt;p&gt;## Acknowledgements&lt;/p&gt;
&lt;p&gt;This issue was identified and reported by Prasanth Sundararajan.&lt;/p&gt;
&lt;p&gt;## Embargo List&lt;/p&gt;
&lt;p&gt;If your organization runs Step CA in production and would like advance, embargoed notification of future security updates, visit https://u.step.sm/disclosure to request inclusion on our embargo list.&lt;/p&gt;
&lt;p&gt;Stay safe, and tha…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q4r8-xm5f-56gw</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-30836</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-30836</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: golang-github-smallstep-certificates, Ubuntu:25.10: golang-github-smallstep-certificates, Ubuntu:26.04:LTS: golang-github-smallstep-certificates&lt;/p&gt;
&lt;p&gt;Step CA is an online certificate authority for secure, automated certificate management for DevOps. Versions 0.30.0-rc6 and below do not safeguard against unauthenticated certificate issuance through the SCEP UpdateReq. This issue has been fixed in version 0.30.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: golang-github-smallstep-certificates, Ubuntu:25.10: golang-github-smallstep-certificates, Ubuntu:26.04:LTS: golang-github-smallstep-certificates&lt;/p&gt;
&lt;p&gt;Step CA is an online certificate authority for secure, automated certificate management for DevOps. Versions 0.30.0-rc6 and below do not safeguard against unauthenticated certificate issuance through the SCEP UpdateReq. This issue has been fixed in version 0.30.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-30836</guid>
    </item>
  </channel>
</rss>
