Researchers altered a forensic DNA evidence file in 45 minutes and the analysis software raised no warning (CVE-2026-17583)
Researchers altered a forensic DNA evidence file in 45 minutes and the analysis software raised no warning (CVE-2026-17583) Source: https://www.linkedin.com/pulse/researchers-altered-dna-evidence-file-45-minutes-tymoteusz-netter-bxhhf/
Researchers altered a forensic DNA evidence file in 45 minutes and the analysis software raised no warning (CVE-2026-17583)
Description
Researchers altered a forensic DNA evidence file in 45 minutes and the analysis software raised no warning (CVE-2026-17583) Source: https://www.linkedin.com/pulse/researchers-altered-dna-evidence-file-45-minutes-tymoteusz-netter-bxhhf/
Reddit Discussion
Disclosure: I write a daily security newsletter, this was today's issue. The
substance is below, link at the end.
Thermo Fisher's July 31 bulletin covers CVE-2026-17583 (CVSS v4.0 8.2). The
.fsa and .hid files from Applied Biosystems human identification instruments can
be modified between the instrument writing them and the analysis software
loading them, and the change is nearly undetectable. Nothing in the file let the
software confirm the bytes were the ones the instrument wrote. Nathan Adams of
Forensic Bioinformatics told the WSJ his first successful modification took
about 45 minutes, merging scans from two DNA profiles into one file that
presented as untouched since 2015.
The updates add digital signatures, which only protects files written after the
upgrade. The bulletin does not address retroactive validation, the researchers
found no way to detect prior tampering, and these file types have been produced
since 1995. Three end-of-life product lines get no update at all.
Full writeup with the affected versions and remediation order:
Bulletin:
https://documents.thermofisher.com/TFS-Assets/CORP/Product-Guides/fsa_hid_bulletin.pdf
Most of us have outputs a downstream process treats as authoritative without
checking provenance. For files predating any signing mechanism, write-access
logs on the landing directory are the only retrospective evidence I can build.
What are you using?
Technical Details
- Source Type
- Subreddit
- cybersecurity
- Reddit Score
- 0
- Discussion Level
- minimal
- Content Source
- reddit_link_post
- Post Type
- link
- Domain
- null
- Newsworthiness Assessment
- {"score":56,"reasons":["external_link","newsworthy_keywords:cve-,analysis","security_identifier","established_author","recent_news"],"isNewsworthy":true,"foundNewsworthy":["cve-","analysis"],"foundNonNewsworthy":[]}
- Has External Source
- true
- Trusted Domain
- false
Threat ID: 6a7219a2bf8831d539238d1c
Added to database: 08/04/2026, 16:56:02 UTC
Last updated: 08/04/2026, 16:56:02 UTC
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.