ALTCHA Lib Go denial of service via nil-map panic in signature parsing
- Exploited
- No known exploitation
- Fix
- Fixed in 2.1.0
- Who is exposed
- Not reported
Summary
The ALTCHA Go library (altcha-lib-go from altcha-org) can panic when it parses malformed VerificationData during server signature verification. A remote client that isn't logged in can send such a request to abort it, and in applications without panic recovery this can crash the whole process.
Written by a model
Original description
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.
What to do
Upgrade to a fixed version: 2.1.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-103033 (ALTCHA: Nil-map panic (pre-verification DoS) in v1 parseServerSignature on malformed VerificationData), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-103033 (entry last updated 2026-11-19):
Affected:
- altcha-org altcha-lib-go: from 2.0.0, fixed in 2.1.0
Fixed versions: 2.1.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-103033 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-103033 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/altcha-org/altcha-lib-go/security/advisories/GHSA-gfwj-45pc-w6r5
- https://github.com/altcha-org/altcha-lib-go/commit/2c4fc27a7b2d5b89f7175676445efcacc564c27c
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-103033
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-103033"}.Affected versions
- altcha-org altcha-lib-goFrom 2.0.0 · fixed in 2.1.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · altcha-org/altcha-lib-go · Advisory GHSA-gfwj-45pc-w6r5 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-103033 |
| Record | NVD · CVE-2026-103033 |
| Other links 1 | |
| Repository | GitHub · altcha-org/altcha-lib-go · Commit 2c4fc27a |
Questions about CVE-2026-103033
Is CVE-2026-103033 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-103033?
altcha-lib-go: from 2.0.0 before 2.1.0.
Source: cve.now feed data
How do I fix CVE-2026-103033?
Upgrade to a fixed version: 2.1.0.
Source: cve.now feed data
Related
- CVE-2025-68113ALTCHA Proof-of-Work Vulnerable to Challenge Splicing and Replay
- CVE-2026-71481ALTCHA PHP: verifySolution bypasses HMAC signature check when challenge signature is absent
- CVE-2026-133245parse5 7.0.0 before 8.1.1 Denial of Service via Preprocessor#_processSurrogate
- CVE-2026-132140DrayTek Vigor2960 Apmcfg Upload mainfunction.cgi null pointer dereference
- CVE-2026-115578go-guerrilla crashes on a bare XCLIENT command (7-byte slice off-by-one panic)
- CVE-2026-131196Denial of Service (DoS) through Splunk-to-Splunk Data Forwarding in Splunk Enterprise
No corrections so far. Something wrong on this page? Report an error.