CVE-2025-26167 Information disclosure in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2025-26167 and fix it if it is affected.
What it is: CVE-2025-26167 is a high-severity vulnerability in n/a, published on 6 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-26167 exists.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2025-26167/ (Markdown: https://insights.sbomify.com/CVE-2025-26167/index.md)
Unauthenticated attackers can read arbitrary internal files from the Buffalo LS520D NAS web interface.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-26167?
CVE-2025-26167 is a high-severity vulnerability in n/a, published on 6 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Buffalo LS520D 4.53 is vulnerable to Arbitrary file read, which allows unauthenticated attackers to access the NAS web UI and read arbitrary internal files.
Weakness: CWE-200
Which versions are affected by CVE-2025-26167?
How do I fix CVE-2025-26167?
No fix has been published for CVE-2025-26167 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-26167 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-26167 exists.
Sources
Also known as GHSA-pwx5-jwh9-q63q.