cve.bz

CVE-2025-68113 altcha-org altcha-lib: Misinterpretation of Input

6.5 mediumEPSS 0.5%Fix available

Medium (6.5) in altcha-org altcha-lib. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in altcha-lib 1.4.1.

On this page
ALTCHA is privacy-first software for captcha and bot protection. A cryptographic semantic binding flaw in ALTCHA libraries allows challenge payload splicing, which may enable replay attacks. The HMAC signature does not unambiguously bind challenge parameters to the nonce, allowing an attacker to reinterpret a valid proof-of-work submission with a modified expiration value. This may allow previously solved challenges to be reused beyond their intended lifetime, depending on server-side replay handling and deployment assumptions. The vulnerability primarily impacts abuse-prevention mechanisms such as rate limiting and bot mitigation. It does not directly affect data confidentiality or integrity. This issue has been addressed by enforcing explicit semantic separation between challenge parameters and the nonce during HMAC computation. Users are advised to upgrade to patched versions, which include version 1.0.0 of the altcha Golang package, version 1.0.0 of the altcha Rubygem, version 1.0.0 of the altcha pip package, version 1.0.0 of the altcha Erlang package, version 1.4.1 of the altcha-lib npm package, version 1.3.1 of the altcha-org/altcha Composer package, and version 1.3.0 of the org.altcha:altcha Maven package. As a mitigation, implementations may append a delimiter to the end of the `salt` value prior to HMAC computation (for example, `<salt>?expires=<time>&`). This prevents ambiguity between parameters and the nonce and is backward-compatible with existing implementations, as the delimiter is treated as a standard URL parameter separator.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd 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 2025-12-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-115 Misinterpretation of Input
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures, A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • altcha-lib (npm): fixed in 1.4.1
  • altcha-org/altcha (Packagist): fixed in 1.3.1
  • github.com/altcha-org/altcha-lib-go (Go): fixed in 1.0.0
  • org.altcha:altcha (Maven): fixed in 1.3.0
  • altcha (RubyGems): fixed in 1.0.0
  • altcha (PyPI): fixed in 1.0.0
  • altcha (Hex): fixed in 1.0.0
  • openSUSE: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2025-68113 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68113?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68113?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-2025-68113 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< 1.4.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6gvq-jcmp-8959npmaltcha-lib<1.4.11.4.1
GHSA-6gvq-jcmp-8959Packagistaltcha-org/altcha<1.3.11.3.1
GHSA-6gvq-jcmp-8959Gogithub.com/altcha-org/altcha-lib-go<1.0.01.0.0
GHSA-6gvq-jcmp-8959Mavenorg.altcha:altcha<1.3.01.3.0
GHSA-6gvq-jcmp-8959RubyGemsaltcha<1.0.01.0.0
GHSA-6gvq-jcmp-8959PyPIaltcha<1.0.01.0.0
GHSA-6gvq-jcmp-8959Hexaltcha<1.0.01.0.0
GO-2025-4239Gogithub.com/altcha-org/altcha-lib-go<1.0.01.0.0
PYSEC-2026-1115PyPIaltcha<1.0.01.0.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 15.6govulncheck-vulndb0.0.20251230T014957-150000.1.134.1SUSE-SU-2026:0037-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

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