Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local workstation access (insider or physical)
-
DeliveryLocate .fsa/.hid files in instrument output directory
-
ExploitEdit DNA allele or sequence data using file editor
-
ExecutionNo integrity check detects modification
-
PersistDownstream GeneMapper/analysis software imports falsified file
-
ImpactIncorrect DNA test result reported as authoritative
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Integrity check implementation
|
| Exploitation Conditions | Exploitation requires local file system access to the directory where .fsa or .hid output files are stored on the workstation connected to the affected genetic analyzer instrument. The CVSS 4.0 vector specifies PR:N, meaning no elevated operating system privileges are needed - any standard local user account with read-write permissions on the output directory can perform the modification. The vulnerability is present across the default output pipeline: no special configuration, feature flag, or non-default mode is required because the integrity check is absent by design across all affected product versions. Exploitation is limited to actors with physical or remote desktop access to the instrument-connected workstation; network-remote unauthenticated exploitation is not possible given AV:L. The ABI PRISM 310 and 3100 series are legacy platforms likely in end-of-life deployments, which may have weaker surrounding access controls and patch management, increasing insider-threat risk in those environments. |
| Impact | The CVSS 4.0 score of 8.3 (AV:L/AC:L/AT:N/PR:N/UI:N with VI:H/VA:H and SI:H) reflects low attack complexity and no authentication requirement once file system access exists, but the local attack vector (AV:L) substantially limits the exposed attack surface compared to network-exploitable vulnerabilities. EPSS data was not provided; given the specialized deployment context and absence of KEV listing, opportunistic exploitation at scale is unlikely. The real-world risk is domain-specific but severe: in forensic laboratories using GeneMapper ID-X, a tampered .hid file could alter a DNA profile used as criminal evidence; in clinical Sanger sequencing environments, a modified .fsa file could change a variant call. The VA:H metric in the provided vector may reflect scenarios where corrupted files render the analysis pipeline unable to process results, effectively making the instrument's output unusable. No conflicting signals exist between the CVSS vector and description. The absence of KEV listing and public POC reduces urgency for most deployments, but the potential for high-consequence, low-detectability fraud in forensic or clinical contexts elevates mission-critical risk independent of EPSS probability. |
| Exploit ScenarioDerived | A lab technician or insider adversary with standard user access to the workstation connected to a forensic DNA analyzer opens a .hid output file in a hex editor or .fsa-compatible viewer and alters allele peak calls to match a desired DNA profile. Because the GeneMapper ID-X software performs no signature or checksum validation on import, it processes the modified file identically to authentic instrument output, and the falsified STR profile is reported as a match or exclusion in a case report. No exploit code is required - the attack is a manual file edit requiring only knowledge of the file format. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 05, 2026
Integrity tampering in Thermo Fisher Applied Biosystems Genetic Analyzers allows any user with local file system access to silently modify .fsa and .hid output files - the raw DNA sequence and fragment analysis data produced by these instruments - because no cryptographic integrity check (CWE-353) is applied to these files. Affected products span eight distinct data collection and analysis software lines, including the forensic-grade GeneMapper ID-X platform, meaning tampered files could propagate falsified DNA profiles into criminal proceedings or clinical diagnostics without detection. No public exploit code has been identified at time of analysis, and exploitation is covered by CISA ICS Medical Advisory ICSMA-26-216-01.
RemediationAI
Consult the Thermo Fisher vendor bulletin at https://documents.thermofisher.com/TFS-Assets/CORP/Product-Guides/fsa_hid_bulletin.pdf and CISA ICSMA-26-216-01 at https://www.cisa.gov/news-events/ics-medical-advisories/icsma-26-216-01 for vendor-recommended patched versions; the version caps listed in EUVD indicate the last vulnerable versions for each product line, and upgraded releases may be available. Until patching is confirmed, restrict file system write access to .fsa and .hid output directories using OS-level access controls (NTFS or filesystem ACLs), limiting write permissions exclusively to the instrument data collection service account and authorized analysts - this directly reduces who can tamper with files, with the trade-off that overly restrictive permissions may disrupt automated analysis pipelines. Implement file integrity monitoring (FIM) on the output directories using a tool such as Tripwire, OSSEC, or Windows File Integrity Monitoring so that any post-generation modification to .fsa/.hid files triggers an alert; this does not prevent tampering but enables detection. For forensic use cases (GeneMapper ID-X deployments), establish a chain-of-custody logging procedure that records file hash values (SHA-256) at the time of instrument transfer and re-validates them prior to any downstream use - this compensates for the missing built-in integrity check at the procedural level. Restrict physical and logical access to workstations connected to these instruments, given the local attack vector.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 8 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Affected products are the data collection and downstream analysis software suites bundled with Thermo Fisher Scientific's capillary electrophoresis (CE) genetic analyzer instruments. These instruments generate .fsa (fragment size analysis) and .hid (human identity data) binary output files - proprietary formats containing raw electropherogram signal data, size-called allele tables, and associated metadata. CWE-353 (Missing Support for Integrity Check) identifies the root cause: neither the instrument software nor downstream analysis tools cryptographically sign or checksum these output files after generation, so post-generation edits are indistinguishable from authentic instrument output. Affected CPEs span the full Applied Biosystems capillary instrument family: the 3500/3500xL, 3730/3730xL, SeqStudio, SeqStudio Flex, 3130, ABI PRISM 3100/3100-Avant, and ABI PRISM 310 Data Collection Software lines, as well as the GeneMapper ID-X Software used for forensic STR profiling. The vulnerability is architectural: the file format and pipeline were designed without tamper-evidence, not as a result of a specific code defect.
Know when Applied Biosystems 3500 3500Xl Series Data Collection Software gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:N
Local file edit requires no privileges (PR:N); scope changes (S:C) because falsified DNA data impacts downstream forensic/clinical decisions beyond the instrumented system; no confidentiality or availability impact from mere file modification.
Primary rating from Vendor (icscert).
CVSS VectorVendor: icscert
Lifecycle Timeline
2DescriptionCVE.org
The affected
Thermo Fisher Applied Biosystems Genetic Analyzers are vulnerable because .fsa/.hid output files can be edited. An attacker could tamper with these files, altering DNA data and resulting in inaccurate DNA test outcomes.
Executive ViewAI
Thermo Fisher Applied Biosystems Genetic Analyzers lack cryptographic integrity controls on DNA sequence output files, allowing any local user to silently modify forensic and clinical data-including GeneMapper ID-X-without detection. Organizations using these systems (law enforcement, forensic labs, clinical labs) face material risk of falsified DNA profiles entering criminal proceedings and medical records, creating significant liability for wrongful convictions and patient harm.
No vendor-released patch identified at time of analysis. Interim mitigations include: (1) restrictive file system access controls limiting write access to authenticated instruments and authorized personnel only; (2) external cryptographic integrity verification (SHA-256 or digital signatures) for all output files, stored separately and verified at time of analysis/use; (3) centralized audit logging of all file access and modifications; (4) network isolation of genetic analyzer systems and output storage where operationally feasible; (5) multi-factor authentication for administrative access to systems storing analyzer output; (6) regular integrity audits comparing file hashes against secured baselines.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-53616
GHSA-5p87-q7f6-jf7x
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB