Loading...
Skip to main content

CVE-2025-68113 — Vulnerability in org.altcha:altcha — CVE Details

MEDIUM

ALTCHA Proof-of-Work Vulnerable to Challenge Splicing and Replay

Published December 16, 2025Updated September 10, 2026Source: osv

Summary

### Impact 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. ### Patches 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. ### Workarounds 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.

Advisory Timeline

  • First published December 16, 2025 (300 days ago).
  • Last revised September 10, 2026 — 268 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Maven
Update org.altcha:altcha to 1.3.0 or later
<!-- Update pom.xml dependency version to 1.3.0 for org.altcha:altcha -->
npm
Update altcha-lib to 1.4.1 or later
npm install altcha-lib@1.4.1
Bundler
Update altcha to 1.0.0 or later
gem install altcha -v 1.0.0
pip
Update altcha to 1.0.0 or later
pip install "altcha>=1.0.0"
Go
Update github.com/altcha-org/altcha-lib-go to 1.0.0 or later
go get github.com/altcha-org/altcha-lib-go@v1.0.0
Composer
Update altcha-org/altcha to 1.3.1 or later
composer require "altcha-org/altcha:^1.3.1"

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (6)

Affects 6 ecosystems: go (1), maven (1), npm (1), packagist (1), pypi (1), rubygems (1).

PackageEcosystemAffectedFixed In
org.altcha:altcha
maven
1.1.0, 1.1.1, 1.1.2, 1.2.01.3.0
altcha-lib
npm
All versions1.4.1
altcha
rubygems
0.1.0, 0.2.0, 0.2.11.0.0
altcha
pypi
0.1.0, 0.1.2, 0.1.3, 0.1.4 (+6 more)1.0.0
github.com/altcha-org/altcha-lib-go
go
All versions1.0.0
altcha-org/altcha
packagist
v0.1.0, v0.1.1, v0.1.2, v0.1.3 (+7 more)1.3.1

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 6.5 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Frequently Asked Questions

What is CVE-2025-68113?
ALTCHA Proof-of-Work Vulnerable to Challenge Splicing and Replay This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 6.5/10).
How do I check if my project is affected by CVE-2025-68113?
CVE-2025-68113 affects org.altcha:altcha, altcha-lib and altcha (and 2 more). Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2025-68113 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
6.5

Exploitation requires specific conditions or has limited impact. Remediate within weeks.

Also Known As

GHSA-6gvq-jcmp-8959
GO-2025-4239
PYSEC-2026-1115

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies