CVE
TÜBİTAK BİLGEM Pardus About local privilege escalation via polkit
- Exploited
- No known exploitation
- Fix
- Fixed in 1.2.5
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.2.5.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.10% · 0th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 8/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
Pardus About, a product from TÜBİTAK BİLGEM Software Technologies Research Institute, contains an incorrect authorization flaw that lets a local user with low-privilege access escalate their privileges. The attacker must already have a local login on the system, and no user interaction is needed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Incorrect Authorization vulnerability in TÜBİTAK BİLGEM Software Technologies Research Institute Pardus About allows Privilege Escalation.
This issue affects Pardus About: before 1.2.5.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.8/10CVSS 7.8
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.2.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-87772 (Unauthenticated Polkit Privilege Escalation in TÜBİTAK BİLGEM's Pardus About), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-87772 (entry last updated 2026-11-12):
Affected:
- TÜBİTAK BİLGEM Software Technologies Research Institute Pardus About: fixed in 1.2.5
Fixed versions: 1.2.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-87772 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-87772 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1521
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-87772
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-87772"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- TÜBİTAK BİLGEM Software Technologies Research Institute Pardus About
fixed in 1.2.5
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-87772
Is CVE-2026-87772 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-87772?
Pardus About: before 1.2.5.Source: cve.now feed data
How do I fix CVE-2026-87772?
Upgrade to a fixed version: 1.2.5.Source: cve.now feed data