Threats / Soliton Systems K.K / CVE-2026-25108
CVE-2026-25108
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Soliton Systems K.K FileZen vulnerability
Soliton Systems FileZen contains an OS command injection vulnerability triggered via specially crafted HTTP requests during user login, enabling arbitrary command execution.
Verdict
Today item — known-exploited.
An authenticated attacker can inject operating system commands through malformed HTTP requests to FileZen, achieving code execution with the privileges of the application process. Active exploitation has been observed in the wild.
CISA KEV Yes · 2026-02-245EPSS 0.04979 (verify live)6CVSS 8.73CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-02-24).
Probability (EPSS)
EPSS 0.04979 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.7 (CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) · Affected: Soliton Systems K.K, FileZen. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 11 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious HTTP request containing shell metacharacters and inject it during the login process to bypass input validation.
Business
Unauthorized code execution within the FileZen application environment compromises data confidentiality and system integrity.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary operating system commands with the privileges of the FileZen process to establish persistence or pivot to adjacent systems.
Business
Attackers gain foothold for lateral movement, data exfiltration, or deployment of secondary payloads across the infrastructure.
3
Lateral reach — past segmentation narrative 3
Attacker
I enumerate system resources, modify file permissions, or disable security controls to deepen access.
Business
Organizational security posture degrades as attackers consolidate control and prepare for sustained compromise.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05