cve.bz

CVE-2026-71481 ALTCHA PHP: verifySolution bypasses HMAC signature check when challenge signature is absent

7.5 highEPSS 0.3%Fix available

High (7.5) in altcha-org altcha-lib-php. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in altcha-org/altcha 2.0.3.

On this page
ALTCHA PHP is a lightweight PHP library for creating and verifying ALTCHA challenges. From 2.0.0 until 2.0.3, the verifySolution method skips HMAC signature verification when a challenge payload omits the signature field, even when hmacSignatureSecret is configured. An attacker can remove the signature, supply attacker-selected low-difficulty challenge parameters, solve the resulting proof of work, and submit a payload that verifies successfully, bypassing the CAPTCHA control. This issue is fixed in version 2.0.3.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 21st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • altcha-org/altcha (Packagist): fixed in 2.0.3

Ask an AI about this CVE

Show the promptExplain CVE-2026-71481 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-71481?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-71481?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-71481 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
altcha-org altcha-lib-php>= 2.0.0, < 2.0.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-82w8-65qw-gch6Packagistaltcha-org/altcha>=2.0.0 <2.0.32.0.3

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • LLCForge/CVE-2026-71481 Harbor Check: matches CVE 0 stars, Python, created
    altcha CAPTCHA HMAC signature bypass allows bot automation without valid signature. High.

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON