NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2025-68113: ALTCHA Proof-of-Work Vulnerable to Challenge Splicing and Replay

mediumCVSS 3.1 6.5GHSA-6gvq-jcmp-8959

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.

Published Dec 16, 2025 · Updated Dec 20, 2025

Affected packages

altcha-lib

Ecosystem
npm
Affected
< 1.4.1
Fixed in
1.4.1
Check
npm ls altcha-lib

altcha-org/altcha

Ecosystem
Composer (PHP)
Affected
< 1.3.1
Fixed in
1.3.1
Check
composer show altcha-org/altcha

github.com/altcha-org/altcha-lib-go

Ecosystem
Go
Affected
< 1.0.0
Fixed in
1.0.0
Check
go list -m github.com/altcha-org/altcha-lib-go

org.altcha:altcha

Ecosystem
Maven
Affected
< 1.3.0
Fixed in
1.3.0
Check
mvn dependency:tree -Dincludes=org.altcha:altcha

altcha

Ecosystem
RubyGems
Affected
< 1.0.0
Fixed in
1.0.0
Check
bundle info altcha

altcha

Ecosystem
PyPI
Affected
< 1.0.0
Fixed in
1.0.0
Check
pip show altcha

altcha

Ecosystem
Erlang (Hex)
Affected
< 1.0.0
Fixed in
1.0.0

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to eternal-flame-AD.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries