CVE-2026-103033
### Summary `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&%zz=2`). 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. ### Impact 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. ### Proof Of Concept ```go payload, _ := json.Marshal(ServerSignaturePayload{ Algorithm: SHA256, VerificationData: "x=1&%zz=2", Signature: "irrelevant", Verified: true, }) encoded := base64.StdEncoding.EncodeToString(payload) VerifyServerSignature(encoded, "some-secret") // panics: assignment to entry in nil map ``` ### Patch `Extra` is now initialized unconditionally before the `url.ParseQuery` error check, so it's always safe to write into regardless of parse errors. ### Workarounds Recover from panics around calls to `VerifyServerSignature`/`VerifyServerSignatureSafe`, or reject/sanitize `VerificationData` before calling them
Properties
- Severity
- medium
- Summary
- ALTCHA: Nil-map panic (pre-verification DoS) in v1 parseServerSignature on malformed VerificationData
- Nvd fetched at
- 2026-11-22T12:30:49.958423+00:00
- Epss score
- 0.00407
- Cvss severity
- MEDIUM
- Cvss score
- 5.3
- Retrieved at
- 2026-11-22T12:32:25+00:00
- Ghsa published
- 2026-11-20T00:21:19Z
- Source url
- https://github.com/advisories/GHSA-gfwj-45pc-w6r5
- Ghsa updated
- 2026-11-20T00:21:20Z
- Ghsa id
- GHSA-gfwj-45pc-w6r5
- Last source
- FIRST EPSS
- Score
- 5.3
- Cvss version
- 3.1
- Cve id
- CVE-2026-103033
- Cvss vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- First seen by Signal
- 2026-11-19T23:31:53+00:00
- Name
- CVE-2026-103033
- Is ghsa only
- false
- Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Related Entities (4)
HAS_WEAKNESS (2)
AFFECTS (1)
VULNERABLE_TO (1)
Related research
Explore deeper with Ninja Signal's threat intelligence graph