Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local login on host
-
DeliveryPre-plant malicious symlink at target path
-
ExploitTrigger privileged scanner driver write
-
ExecutionDriver follows symlink
-
PersistOverwrite arbitrary root-owned file
-
ImpactEscalate privileges or deny service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Symlink resolution safety
|
| Exploitation Conditions | Exploitation requires the attacker to already have a local login on the Linux system where the Image Scanner Driver for Linux (fi series or sp series) is installed (AV:L, PR:L). The attacker must pre-position a symbolic link ('a special method in advance') so that a privileged driver operation follows it and overwrites an arbitrary file; success also depends on the victim/privileged process performing the vulnerable write (UI:P passive interaction). Limiting factors: no network vector, no unauthenticated path, and the target file overwrite only yields integrity/availability impact - there is no confidentiality impact. Exploitation is confined to hosts that have this specific PFU/Ricoh scanner driver installed. |
| Impact | This is a genuinely medium-risk local privilege/integrity issue, not a high-CVSS-but-hollow finding - but it is also not a top-tier priority because it cannot be exploited remotely. The vendor CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:P) scores 5.2, and the metrics are internally consistent with the description: the attacker must already be able to log in to the Linux host (AV:L, PR:L), and exploitation depends on a privileged component acting on an attacker-planted symlink (UI:P - passive interaction by the victim/service). Impact is integrity and availability only (VI:H/VA:H, VC:N), matching a CWE-59 link-following file-overwrite primitive rather than a data-theft bug. No EPSS score, no CISA KEV listing, and no public POC are present in the supplied data, so exploitation status is 'no public exploit identified at time of analysis.' The main signal to weigh is that all remote/network signals are absent - this requires an existing local foothold - which sharply limits real-world urgency despite the arbitrary-overwrite (potentially root-level, hence privilege-escalation-capable) impact. Note the 'Information Disclosure' tag conflicts with the CVSS impact metrics (VC:N/C:N), so it should not drive triage. |
| Exploit ScenarioDerived | A user with a local login on a Linux host running the PFU/Ricoh Image Scanner Driver pre-plants a symbolic link ('a special method in advance') at a path the driver's privileged component later writes to. When the scanner driver or its helper process performs that write, it follows the attacker's symlink and overwrites an arbitrary file (e.g. a root-owned configuration or binary), enabling privilege escalation or denial of service. No public exploit code was identified in the provided data, and exploitation requires the attacker to already possess local access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Arbitrary file overwrite in the PFU/Ricoh Image Scanner Driver for Linux (fi series and sp series) lets an authenticated local user destroy or corrupt files that the driver's privileged operation writes to, by pre-positioning a symbolic link that the driver later follows. The vendor rates this CVSS 4.0 5.2 (AV:L/AC:L/AT:N/PR:L/UI:P), and our independent CVSS 3.1 assessment is AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H - a local-only integrity and availability issue with no confidentiality impact and no remote or unauthenticated path. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; exposure is limited to Linux hosts that actually have this specific PFU/Ricoh scanner driver installed.
RemediationAI
No exact fixed version is confirmed in the available data, so treat patch status as unverified and check the vendor advisory at https://www.pfu.ricoh.com/global/products_security/vul2026000001e.html together with JVN JVNVU96968110 (https://jvn.jp/en/vu/JVNVU96968110/) for the current release that addresses the link-following behavior. If no scanner is in use on a given host, removing or disabling the driver package is the most effective mitigation and carries no functional trade-off. Where the driver must stay installed, enable the kernel symlink hardening sysctl fs.protected_symlinks=1, which blocks symlink-following in world-writable sticky directories such as /tmp (trade-off: it does not protect paths inside directories the attacker already owns, so pair it with restrictive permissions on the driver's working, spool, and configuration directories). Restrict local shell and sudo access to trusted users only, since exploitation requires an existing login (AV:L/PR:L), and monitor or restrict the driver's privileged write paths with a file-integrity or audit rule so unexpected changes to system files are detected; the trade-off there is added audit noise and possible performance overhead on I/O-heavy hosts.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-59 (Improper Link Resolution Before File Access), the classic symbolic-link-following class on Linux: a privileged component of the scanner driver package (installer, helper binary, daemon, or udev-triggered script) opens a predictable filesystem path for writing without using O_NOFOLLOW / AT_SYMLINK_NOFOLLOW or verifying that the resolved target is trusted. An attacker with an existing local account plants a symlink at that predictable location in advance; when the privileged driver operation runs, it follows the link and writes to whatever the link points at, giving a controlled file overwrite with the privileges of that operation. The CPE data confirms two affected product families, cpe:2.3:a:pfu_limited:image_scanner_driver_for_linux_(fi_series) and cpe:2.3:a:pfu_limited:image_scanner_driver_for_linux_(sp_series), both with wildcarded versions, meaning no specific fixed version boundary is published in the affected-product data. The CVSS 4.0 vector supplied by the vendor uses PR:L and UI:P, matching our assessment that the attacker must already be logged in locally and that success depends on the privileged write actually being performed.
Know when Image Scanner Driver For Linux Fi Series 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:L/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
Requires an existing local login (AV:L/PR:L) and a privileged process to act on a pre-planted symlink (UI:R); arbitrary file overwrite gives I:H/A:H with no confidentiality impact.
Primary rating from Vendor (jpcert).
CVSS VectorVendor: jpcert
Lifecycle Timeline
1DescriptionCVE.org
Image Scanner Driver for Linux contains a link following vulnerability. An attacker who can log in to a Linux system where the product is installed may overwrite arbitrary files by using a special method in advance.
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.
EUVD-2026-89568
GHSA-95pw-7mxv-57v2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB