<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-22T18:30:47.099409+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-410062</id>
    <title>EUVD-2026-410062</title>
    <updated>2026-11-22T18:30:47.101902+00:00</updated>
    <content>EUVD-2026-410062</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-410062"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-103033</id>
    <title>fkie_cve-2026-103033</title>
    <updated>2026-11-22T18:30:47.101932+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>ALTCHA is a Go library for creating and verifying ALTCHA challenges. Prior to 2.1.0, parseServerSignature can leave ServerSignatureVerificationData.Extra uninitialized when url.ParseQuery returns partial values and an error for a malformed percent escape in VerificationData. A later write of an unknown parsed key to the nil map panics before VerifyServerSignature or VerifyServerSignatureSafe completes signature verification, so an unauthenticated client can abort a request. Standard net/http recovers the request goroutine, while application goroutines or frameworks without recovery can crash the process. This issue is fixed in version 2.1.0.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-103033"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-gfwj-45pc-w6r5</id>
    <title>GHSA-gfwj-45pc-w6r5 — ALTCHA: Nil-map panic (pre-verification DoS) in v1 parseServerSignature on malformed VerificationData</title>
    <updated>2026-11-22T18:30:47.101962+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/altcha-org/altcha-lib-go/v2</p>
<p>### Summary</p>
<p>`parseServerSignature` in the v1 module only initializes `ServerSignatureVerificationData.Extra` inside the `if err == nil` branch after `url.ParseQuery(parsedPayload.VerificationData)`. Go's `url.ParseQuery` returns the successfully-parsed pairs together with a non-nil error when the query string contains a malformed percent-escape. A subsequent loop unconditionally writes unknown keys into `Extra`, regardless of `err`, causing a nil-map write panic (assignment to entry in nil map) whenever an attacker supplies a `VerificationData` string with a bad %-escape (e.g. `x=1&amp;%zz=2`).</p>
<p>This is reachable pre-authentication: `parseServerSignature` is called by the exported `VerifyServerSignature` / `VerifyServerSignatureSafe` before any HMAC/signature check, and `VerificationData` is attacker-controlled data forwarded by the client as part of the ALTCHA server-signature payload.</p>
<p>### Impact</p>
<p>Any application calling `VerifyServerSignature` or `VerifyServerSignatureSafe` on unauthenticated input can be made to panic by submitting a crafted payload. Under standard net/http, the per-request goroutine panic is recovered and the request aborts (a log-flood / per-request DoS); it escalates to a full process crash if verification runs in an application-spawned goroutine or a non-recovering framework.</p>
<p>### Proof Of Concept</p>
<p>```go
payload, _ := json.Marshal(ServerSignaturePayload{
    Algorithm:        SHA256,
    VerificationData: "x=1&amp;%zz=2",
    Signature:        "irrelevant",…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-gfwj-45pc-w6r5"/>
  </entry>
</feed>
