Loading story…
A critical vulnerability (CVE-2025-12816) was discovered in the popular JavaScript cryptography library node-forge, which is downloaded over 20 million times per week. The flaw allows attackers to bypass signature verification by exploiting an interpretation-conflict in the library's ASN.1 validation mechanism, enabling malformed data to pass as valid even when cryptographically invalid. This vulnerability could allow unauthenticated attackers to craft ASN.1 structures that desynchronize schema validations, potentially bypassing cryptographic verifications and security decisions in applications relying on node-forge.
The issue was responsibly disclosed by a researcher from Palo Alto Networks, and a fix was released in version 1.3.2 of node-forge. Security advisories from CERT-CC warn that the impact varies by application, but may include authentication bypass, signed data tampering, and misuse of certificate-related functions. Developers using node-forge are strongly advised to update to the latest version immediately to mitigate the risk, as the vulnerability could have significant consequences in environments where cryptographic verification is central to trust decisions.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
4 events from the most recent confirmed update back to the earliest known activity.
A pull request in Google's security research repository updated a frontend component from node-forge 1.3.1 to 1.3.2, reflecting downstream adoption of the patched version. This indicates maintainers began remediating exposure after the fix became available.
Public reporting described how malformed ASN.1 input can desynchronize validation and downstream processing, allowing signature verification bypass in applications using node-forge. Coverage highlighted the library's broad adoption, with roughly 21 to 26 million weekly downloads, increasing the potential impact.
A fix for the signature verification bypass issue was released in node-forge version 1.3.2. Developers were advised to upgrade from affected versions because the bug could enable authentication bypass, signed data tampering, and certificate-related misuse depending on application context.
Hunter Wodzenski of Palo Alto Networks identified an ASN.1 interpretation-conflict vulnerability in node-forge that could let malformed data bypass signature verification, and responsibly disclosed it with a proof-of-concept. The flaw was tracked as CVE-2025-12816 and affects node-forge 1.3.1 and earlier.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
github.com
Open sourcesecurityonline.info
Open sourcebleepingcomputer.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Three high-severity vulnerabilities have been disclosed in the JavaScript cryptography library **jsrsasign**, all affecting versions before `11.1.1` and exposing DSA implementations to signature forgery and private key compromise. `CVE-2026-4600` stems from improper verification in DSA domain-parameter validation within `KJUR.crypto.DSA.setPublic` and related DSA/X.509 verification code, allowing attackers to supply malicious parameters such as `g=1` and `y=1` so forged DSA signatures or X.509 certificates are accepted as valid. The issue is classified as `CWE-347` and carries high confidentiality and integrity impact. Two additional flaws can expose DSA private keys during signing. `CVE-2026-4601` affects `KJUR.crypto.DSA.signWithMessageHash`, where the library can emit invalid signatures when `r` or `s` becomes zero instead of retrying, creating a path to recover the private key. `CVE-2026-4599` affects versions from `7.0.0` through versions before `11.1.1` and is tied to incomplete comparison logic in `getRandomBigIntegerZeroToMax` and `getRandomBigIntegerMinToMax`, which can accept out-of-range values, bias DSA nonces, and likewise enable key recovery. The disclosures were accompanied by upstream commits, pull requests, public writeups, and Snyk advisories, with all three bugs rated for high confidentiality and integrity impact and no direct availability impact.
Jun 29, 2026
The Node.js project released security updates across its supported `22.x`, `24.x`, and `26.x` lines to fix 12 vulnerabilities, including two high-severity issues that prompted calls for immediate patching. The most serious bugs are **CVE-2026-48618**, a TLS hostname verification flaw caused by improper handling of Unicode dot separators that can lead to authentication bypass, and **CVE-2026-48933**, a WebCrypto AES integer overflow that can crash processes and enable remote denial-of-service. The releases were announced for all active Node.js lines through the project’s coordinated June security update process and public notices on the `oss-sec` mailing list.
Jun 29, 2026
A **maximum-severity authentication bypass** was disclosed in *pac4j*’s JWT component (*pac4j-jwt*), tracked as **CVE-2026-29000**, affecting a widely used Java security engine embedded across many downstream software packages. The issue is a **logic flaw** that enables attackers to bypass authentication controls by crafting tokens/claims in a way that defeats expected verification, raising concern because exploitation can be relatively straightforward and the library’s transitive use complicates exposure tracking and patch rollout across dependent applications. Public **proof-of-concept (PoC)** code is available, and reporting indicates an attacker who can obtain a target server’s **RSA public key** (often publicly accessible) can forge a **JWE-wrapped PlainJWT** containing arbitrary `sub` and role claims to bypass signature verification and authenticate as any user, including administrators. The pac4j maintainer disclosed the defect and released patched versions shortly after private reporting; while there were no confirmed in-the-wild exploits at the time of reporting, defenders should expect downstream vendors and application owners to issue their own advisories and updates as they assess inherited risk from bundled pac4j versions.
Jun 29, 2026