Skip to main content
VulnerabilityPublished

CVE-2025-59334: mohammadzain2008 Linkr · Improper Verification of Cryptographic Signature

Affects mohammadzain2008 LinkrSource CVE Database V5

0

Not known to be exploited · CVSS 9.7 Critical : upgrade to 2.0.1 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.7Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade mohammadzain2008 Linkr to 2.0.1.

Affected software

ProductAffectedFixed in
mohammadzain2008 LinkrAffected
  • <2.0.1
Fixed in
  • 2.0.1

AI-suggested

  1. Immediate upgrade to Linkr version 2.0.1 or later, which includes manifest integrity verification, is the most effective mitigation.
  2. Until upgrading, restrict usage of Linkr manifests to those obtained from trusted sources only.
  3. Implement manual verification of manifest checksums before extraction to detect tampering.
  4. Host manifests exclusively on secure, trusted servers with strong access controls and monitoring to prevent unauthorized modifications.
  5. Educate users about the risks of extracting files from untrusted manifests and train them to recognize suspicious files or URLs.
  6. Employ network security controls such as web filtering and intrusion detection to block access to known malicious URLs.
  7. Monitor Linkr usage logs for unusual manifest downloads or extraction activities.
  8. Consider application whitelisting or endpoint protection solutions to prevent execution of unauthorized binaries or scripts downloaded via Linkr.
  9. Integrate manifest verification into automated deployment pipelines to enforce integrity checks before file extraction.

Description

Linkr is a lightweight file delivery system that downloads files from a webserver. Linkr versions through 2.0.0 do not verify the integrity or authenticity of .linkr manifest files before using their contents, allowing a tampered manifest to inject arbitrary file entries into a package distribution. An attacker can modify a generated .linkr manifest (for example by adding a new entry with a malicious URL) and when a user runs the extract command the client downloads the attacker-supplied file without verification. This enables arbitrary file injection and creates a potential path to remote code execution if a downloaded malicious binary or script is later executed. Version 2.0.1 adds a manifest integrity check that compares the checksum of the original author-created manifest to the one being extracted and aborts on mismatch, warning if no original manifest is hosted. Users should update to 2.0.1 or later. As a workaround prior to updating, use only trusted .linkr manifests, manually verify manifest integrity, and host manifests on trusted servers.

References

Community reviews

Loading reviews…