CVE-2026-5161Disclosure

LOWCVSS 8.8 · HIGH

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD 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.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-59

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 2 mentions across 1 observed day

What's happening

  • Technical details provided in 2 signals
  • Disclosure: 2 classified signals
  • 2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d
01122Mentions · 2026-04-29: 2Technical Details · 2026-04-29: 204-29
Signal classification1 categories
Disclosure
2100.0%
Referenced assets2 URLs
By indicator
Full discourse2 posts
  • Infoflowcloud@infoflowcloud
    Disclosure

    🚨*CVE* CVE-2026-5161 Improper link resolution before file access ('link following') vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus About allows Symlink Atta… https://www.cve.org/CVERecord?id=CVE-2026-5161 ----- Traducción: CVE-2026-5161 Ins… http://infoflow.cloud`

    Post summary

    The post announces the CVE‑2026‑5161 vulnerability, describing a symlink link‑resolution flaw in Pardus About that could lead to unauthorized file access.

    0000048
    74 followersView on X
  • CVE@CVEnew
    Disclosure

    CVE-2026-5161 Improper link resolution before file access ('link following') vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus About allows Symlink Atta… https://www.cve.org/CVERecord?id=CVE-2026-5161

    Post summary

    The text provides a basic CVE announcement for CVE-2026-5161, outlining the vulnerability type (improper link resolution leading to symlink attacks) but lacks any mention of PoC, exploit code, or active exploitation claims.

    00000133
    57.3K followersView on X

Explore more