CVE-2026-5161 Improper Authentication in TUBITAK BILGEM's Pardus About
High 8.8
Published
Updated
Check this codebase for CVE-2026-5161 and fix it if it is affected.
What it is: CVE-2026-5161 is a high-severity vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus About, published on 29 Apr 2026.
Exploitation: There is no known exploitation of CVE-2026-5161 in the wild and no public exploit code.
Affected product: TUBITAK BILGEM Software Technologies Research Institute Pardus About. 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-5161/ (Markdown: https://insights.sbomify.com/CVE-2026-5161/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-5161?
CVE-2026-5161 is a high-severity vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus About, published on 29 Apr 2026.
Official description
Improper link resolution before file access ('link following') vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus About allows Symlink Attack.
This issue affects Pardus About: before 1.2.2.
Weakness: CWE-59
Which versions are affected by CVE-2026-5161?
How do I fix CVE-2026-5161?
No fix has been published for CVE-2026-5161 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-5161 being exploited?
There is no known exploitation of CVE-2026-5161 in the wild and no public exploit code.
Sources
Also known as GHSA-jxvm-52qc-qcp4.