CVE-2026-51027 Information disclosure in n/a
Critical 9.9
Published
Updated
Check this codebase for CVE-2026-51027 and fix it if it is affected.
What it is: CVE-2026-51027 is a critical vulnerability in n/a, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51027 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-2026-51027/ (Markdown: https://insights.sbomify.com/CVE-2026-51027/index.md)
A remote attacker can obtain sensitive information from the ft2.php component in FileThingie.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-51027?
CVE-2026-51027 is a critical vulnerability in n/a, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
An issue in FileThingie v.2.5.7 allows a remote attacker to obtain sensitive information via the ft2.php component.
Weakness: CWE-200
Which versions are affected by CVE-2026-51027?
How do I fix CVE-2026-51027?
No fix has been published for CVE-2026-51027 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-51027 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51027 exists.
Sources
Also known as GHSA-ppgq-9wj5-42r6.