Arbitrary file injection via unverified manifests
Published Sep 16, 2025 · Updated Sep 16, 2025
Improper manifest validation in Linkr 2.0.0 and earlier allows remote attackers to inject files through a tampered .linkr manifest. The extractor parses the manifest's FILES entries and downloads their attacker-supplied URLs without verifying the manifest against an author-controlled copy. Exploitation requires a user to run extract on the tampered manifest; downloaded code executes only if the malicious binary or script is later run.
Summary
What happened
Improper manifest validation in Linkr 2.0.0 and earlier allows remote attackers to inject files through a tampered .linkr manifest. The extractor parses the manifest's FILES entries and downloads their attacker-supplied URLs without verifying the manifest against an author-controlled copy. Exploitation requires a user to run extract on the tampered manifest; downloaded code executes only if the malicious binary or script is later run.
The record
- CVE
- CVE-2025-59334
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- mohammadzain2008
- Product
- Linkr
- Classifications
- CWE-20, CWE-347, T1204.002, T1105
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream tampered-manifest reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo