<?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>Sun, 22 Nov 2026 17:57:05 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-408914</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-408914</link>
      <description>EUVD-2026-408914</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-408914</guid>
    </item>
    <item>
      <title>fkie_cve-2026-71481</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-71481</link>
      <description>&lt;p&gt;ALTCHA PHP is a lightweight PHP library for creating and verifying ALTCHA challenges. From 2.0.0 until 2.0.3, the verifySolution method skips HMAC signature verification when a challenge payload omits the signature field, even when hmacSignatureSecret is configured. An attacker can remove the signature, supply attacker-selected low-difficulty challenge parameters, solve the resulting proof of work, and submit a payload that verifies successfully, bypassing the CAPTCHA control. This issue is fixed in version 2.0.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ALTCHA PHP is a lightweight PHP library for creating and verifying ALTCHA challenges. From 2.0.0 until 2.0.3, the verifySolution method skips HMAC signature verification when a challenge payload omits the signature field, even when hmacSignatureSecret is configured. An attacker can remove the signature, supply attacker-selected low-difficulty challenge parameters, solve the resulting proof of work, and submit a payload that verifies successfully, bypassing the CAPTCHA control. This issue is fixed in version 2.0.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-71481</guid>
    </item>
    <item>
      <title>GHSA-82w8-65qw-gch6 — ALTCHA PHP: verifySolution bypasses HMAC signature check when challenge signature is absent</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-82w8-65qw-gch6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: altcha-org/altcha&lt;/p&gt;
&lt;p&gt;In altcha-org/altcha v2, the verifySolution method skips HMAC signature verification when the signature field is absent from the challenge payload, even when hmacSignatureSecret is configured.&lt;/p&gt;
&lt;p&gt;An attacker who strips the signature key from the challenge JSON passes the condition as false, bypassing tamper-detection entirely. The PoW solution check then runs against unverified parameters — allowing an attacker to self-issue a low-difficulty challenge, solve it trivially, and submit a payload that verifies as true.&lt;/p&gt;
&lt;p&gt;Impact:
Complete CAPTCHA bypass on any deployment that sets hmacSignatureSecret (the recommended production configuration).&lt;/p&gt;
&lt;p&gt;Fix:
The check was split so that a missing signature is explicitly rejected when a secret is configured.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: altcha-org/altcha&lt;/p&gt;
&lt;p&gt;In altcha-org/altcha v2, the verifySolution method skips HMAC signature verification when the signature field is absent from the challenge payload, even when hmacSignatureSecret is configured.&lt;/p&gt;
&lt;p&gt;An attacker who strips the signature key from the challenge JSON passes the condition as false, bypassing tamper-detection entirely. The PoW solution check then runs against unverified parameters — allowing an attacker to self-issue a low-difficulty challenge, solve it trivially, and submit a payload that verifies as true.&lt;/p&gt;
&lt;p&gt;Impact:
Complete CAPTCHA bypass on any deployment that sets hmacSignatureSecret (the recommended production configuration).&lt;/p&gt;
&lt;p&gt;Fix:
The check was split so that a missing signature is explicitly rejected when a secret is configured.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-82w8-65qw-gch6</guid>
    </item>
  </channel>
</rss>
