Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach unauthenticated /rest/retrieveFileStream endpoint
-
DeliverySupply parent-directory segments in fullPath/fileName
-
ExploitTraverse out of intended directory
-
ExecutionRead arbitrary files (application.yml)
-
PersistHarvest DB/Redis/Nacos credentials
-
ImpactPivot into backend services
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions beyond network reachability - the /rest/retrieveFileStream endpoint is unauthenticated by design, so exploitation requires only that the Risesoft Digital-Infrastructure fileManager module (versions 9.6.5-9.6.11) be network-accessible to the attacker. The concrete prerequisite is the presence of the vulnerable Y9FileController.retrieveFileStream handler, reached by placing parent-directory ('../') segments in the fullPath and fileName parameters. The primary limiting factor is exposure: impact is confined to reading files readable by the application's service account (confidentiality only - no write or code execution), and real-world risk depends on the instance being reachable from an untrusted network and on sensitive files like application.yml residing within traversable reach. |
| Impact | This is a genuine high-priority issue, not a CVSS-inflated one. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes network-reachable, low-complexity, unauthenticated exploitation with no user interaction, and the description corroborates every one of those metrics - the /rest/retrieveFileStream endpoint is explicitly unauthenticated and exploited via crafted parameters, so the vector and the prose agree (no AV:N-vs-local-access conflict here). Impact is confidentiality-only (VC:H/VI:N/VA:N), consistent with an arbitrary-file-read primitive rather than code execution, which is why the base score is 8.7 (High) rather than Critical. The real-world severity is amplified by what the file read yields: the advisory notes application.yml discloses database, Redis and Nacos credentials, turning a read primitive into a credible stepping stone toward fuller compromise of backend services. No CISA KEV listing and no EPSS score were provided in the input, so exploitation likelihood cannot be quantified from these sources; however, a published VulnCheck advisory and a public HackMD technical write-up exist, lowering the barrier to weaponization. Net: treat as a priority patch for any exposed instance, while recognizing active-exploitation and probability signals (KEV/EPSS) are simply absent rather than reassuringly low. |
| Exploit ScenarioDerived | An unauthenticated attacker sends an HTTP request to the exposed /rest/retrieveFileStream endpoint with parent-directory sequences in the fullPath and fileName parameters to escape the intended file directory. They retrieve application.yml and harvest the embedded database, Redis, and Nacos credentials, which can then be used to pivot into those backend services. Public technical write-ups (HackMD, VulnCheck advisory) describe the flaw in detail, though no packaged exploit tool is identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Unauthenticated path traversal in Risesoft Digital-Infrastructure 9.6.5 through 9.6.11 lets any network-reachable attacker read arbitrary files from the server by placing parent-directory ('../') segments in the fullPath and fileName parameters of the fileManager /rest/retrieveFileStream endpoint, which is unauthenticated by design and backed by the Y9FileController.retrieveFileStream handler. Because the traversable location includes application configuration such as application.yml, successful exploitation exposes database, Redis and Nacos credentials - high confidentiality impact with no write or code-execution component. Both the vendor-source reference and the assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N vector (7.5) confirm no authentication or user interaction is required; no public exploit identified at time of analysis, though a public technical write-up describing the traversal is referenced by VulnCheck.
RemediationAI
No vendor-released patch identified at time of analysis, and none of the supplied references point to a fixed version, so remediation must start with exposure reduction rather than an upgrade. Block or deny external access to /rest/retrieveFileStream at the reverse proxy, API gateway or WAF and restrict the fileManager module to trusted management networks or VPN only; the trade-off is that legitimate file-retrieval functionality for remote clients stops working, so confirm which consumers actually depend on the endpoint before enforcing the rule. Add authentication/authorization in front of the fileManager routes at the gateway layer if the application cannot be patched, accepting that this requires coordinating with existing integrations that currently rely on the endpoint being anonymous. Treat credential exposure as already possible: rotate the database, Redis and Nacos secrets referenced in application.yml and any other configuration reachable from the service's working directory, and audit those systems for unauthorized access using the old values. Run the application under a least-privilege service account that cannot read configuration directories outside its own runtime path, and externalize secrets to environment variables or a secrets manager - this is a defense-in-depth control with a real deployment cost, since misconfigured paths can prevent startup. If source changes are possible, canonicalize the resolved path (for example via Path.normalize/toRealPath) and reject any result that does not remain under the configured file store root. Finally, monitor and alert on requests to /rest/retrieveFileStream containing '../' or encoded traversal sequences in fullPath or fileName; the vendor-source reference is the definitive upstream location for a future fix, and the VulnCheck advisory (https://www.vulncheck.com/advisories/digital-infrastructure-9.6.5-through-9.6.11-path-traversal-via-filemanager-retrievefilestream) and the public write-up (https://hackmd.io/@1ExmmukzRMWN7B4gQ4W-4Q/digital-infrastructure-filemanager-path-traversal-rw) should be rechecked for patch guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic CWE-22 improper limitation of a pathname to a restricted directory, rooted in the Java Spring MVC controller class net.risesoft.y9public.controller.Y9FileController, specifically the retrieveFileStream handler at lines 136-166 of the version 9.6.11 source referenced in the disclosure. The handler builds a filesystem path from the caller-supplied fullPath and fileName request parameters without canonicalizing the result or verifying that the resolved path stays inside the intended storage root; concatenating attacker-controlled '../' segments therefore escapes that root and streams the resolved file back to the caller. The endpoint lives under the y9-digitalbase-module/y9-module-filemanager/risenet-y9boot-webapp-filemanager module and is exposed at /rest/retrieveFileStream, and its unauthenticated reachability is reflected in the CVSS:4.0 vector supplied (PR:N/UI:N) as well as in our independent CVSS:3.1 assessment. Impact is confidentiality-only (VC:H with VI:N/VA:N and S:U) - the application reads and returns files, it does not write, delete, or execute them - so the practical severity is amplified by what sits on disk rather than by memory-corruption-style primitives: application.yml and similar configuration holding database, Redis and Nacos credentials is the highlighted target, and the supplied tags (Path Traversal, Redis) reinforce that credential exposure and downstream lateral movement are the realistic follow-on risk, with those reused credentials potentially reaching infrastructure far beyond the vulnerable host.
Know when Redis 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:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Unauthenticated remote file read over the network with low complexity (PR:N/AC:L/AV:N); arbitrary-file disclosure gives C:H while I and A are unaffected (N).
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
DescriptionCVE.org
Risesoft Digital-Infrastructure 9.6.5 through 9.6.11 contains a path traversal vulnerability in the fileManager Y9FileController.retrieveFileStream handler that allows unauthenticated attackers to read arbitrary files by supplying parent-directory segments in the fullPath and fileName parameters. Attackers can request the unauthenticated /rest/retrieveFileStream endpoint to retrieve files like application.yml, exposing database, Redis and Nacos credentials.
Executive ViewAI
Risesoft Digital-Infrastructure releases 9.6.5 through 9.6.11 contain an unauthenticated file-read flaw that allows any attacker with network reach to pull application configuration files off the server, including application.yml, which holds the database, Redis, and Nacos credentials used by the platform. Because those credentials unlock core backend systems, a single successful request can hand an outside party the keys to production data stores and the service registry, and no vendor patch is currently available. Leadership should treat any reachable instance as a live credential-exposure risk requiring immediate containment and credential rotation.
No vendor-released patch identified at time of analysis. Interim mitigations: block external and partner-network access to the /rest/retrieveFileStream endpoint; filter or reject '../' and encoded traversal sequences in the fullPath and fileName parameters at the WAF/reverse proxy; disable or remove the fileManager component where not required; segment affected hosts from sensitive backends; rotate database, Redis, and Nacos credentials and apply least-privilege scoping; enable logging and alerting for traversal attempts against this endpoint.
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
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Privilege escalation to root in the LiteSpeed User-End cPanel Plugin (versions 2.3 through before 2.4.5) lets attackers
UAF in Redis 8.2.1 via crafted Lua scripts by authenticated users. EPSS 12.4%. Patch available.
It was discovered, that redis, a persistent key-value database, due to a packaging issue, is prone to a (Debian-specific
Memory Corruption was discovered in the cmsgpack library in the Lua subsystem in Redis before 3.2.12, 4.x before 4.0.10,
Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user
Redis before 2.8.21 and 3.x before 3.0.2 allows remote attackers to execute arbitrary Lua bytecode via the eval command.
A buffer overflow in Redis 3.2.x prior to 3.2.4 causes arbitrary code execution when a crafted command is sent. Rated cr
Authenticated remote code execution in OpenC3 COSMOS (Ruby gem 'openc3' versions 5.1.0 through 7.2.1) lets any logged-in
Code injection in OneUptime monitoring via custom JS monitor using vm module. PoC and patch available.
RESP protocol command injection in Predis, the popular PHP client for Redis and Valkey, affects versions 3.0.0-RC1 throu
In applications using jfinal 4.9.08 and below, there is a deserialization vulnerability when using redis,may be vulnerab
An issue was found in Apache Airflow versions 1.10.10 and below. Rated critical severity (CVSS 9.8), this vulnerability
EUVD-2026-98946
GHSA-qqmw-cvh2-5395
NVD
CVE.org
EPSS
Exploit-DB