CVE-2026-103033: altcha-lib-go · Uncaught Exception
Affects altcha-lib-goSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.1.0 when convenient.
Data as of 19 Nov 2026, 20:49 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 2.1.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade altcha-lib-go to 2.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| altcha-orgaltcha-lib-go | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade altcha-lib-go to version 2.1.0 or later, where this issue is fixed. No other mitigation is required as the vulnerability is addressed by this official fix.
Description
A vulnerability in altcha-lib-go versions 2.0.0 up to but not including 2.1.0 allows an unauthenticated client to cause a panic and abort a request due to an uncaught exception. This occurs when malformed percent escapes in verification data cause partial parsing errors, leading to a nil map write and panic before signature verification completes. The issue is fixed in version 2.1.0.