CVE-2026-103033: ALTCHA: Nil-map panic (pre-verification DoS) in v1 parseServerSignature on malformed VerificationData

Published Nov 19, 2026
·
Updated

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.

Affected Software

1 affected component
ALTCHA ALTCHA<2.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.1.0

Event History

Nov 19, 2026
CVE Published
via MITRE·08:21 PM
Data Sourced
via MITRE·08:21 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to process-level impact?

Deployments using ALTCHA versions before 2.1.0 are affected if they process attacker-controlled VerificationData. Standard net/http recovers the panicking request goroutine, but application goroutines or frameworks without panic recovery can allow the panic to crash the process.

2

What does an attacker need to trigger the denial of service?

An unauthenticated client can send malformed VerificationData containing a malformed percent escape that causes url.ParseQuery to return partial values and an error. If a later unknown parsed key is written to the uninitialized Extra map, the application panics before signature verification completes.

3

What should be done if immediate upgrading is not possible?

Ensure the code path handling VerificationData has panic recovery, particularly for application goroutines or frameworks that do not provide it. Treat malformed VerificationData as invalid input and prevent it from reaching the vulnerable parsing and map-write path.

4

How can teams determine whether they are affected?

Check whether the application uses ALTCHA before version 2.1.0 and calls the server-signature verification path with client-supplied VerificationData. Logs may show a panic associated with a nil map during processing of malformed query-style verification data.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203