Skip to main content

Pardus-software CVE-2026-8303

| EUVDEUVD-2026-76114 HIGH
Incorrect Privilege Assignment (CWE-266)
2026-09-11 TR-CERT GHSA-6h27-fj47-54hm
7.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privileged local account
  2. Delivery
    Invoke Pardus-software or its backend service
  3. Exploit
    Trigger incorrect privilege assignment
  4. Execution
    Execute code or access resources as elevated user
  5. Impact
    Full host compromise (C:H/I:H/A:H)

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Privilege assignment review
Exploitation Conditions

Exploitation requires a local user account on a Pardus Linux system running Pardus-software before version 1.0.5 - specifically, the attacker must be authenticated with at minimum a standard (low-privilege) account (PR:L). No network access is required (AV:L). No user interaction by another party is needed (UI:N), and no special configuration beyond the default installation of the vulnerable software is described. Limiting factors: the attacker must have local shell or session access to the target host; remote unauthenticated exploitation is not possible based on the AV:L vector. Scope is contained to the vulnerable system (S:U), so lateral movement to other systems is not a direct consequence of the vulnerability itself.

Impact

Real-world risk is moderate-high for environments running Pardus Linux. The CVSS 7.8 score is appropriate: the AV:L constraint limits exposure to attackers who already have local shell access (e.g., a logged-in user or a process that has achieved code execution at low privilege), but AC:L/PR:L/UI:N indicates exploitation is straightforward once that foothold exists. No KEV listing and no public POC have been identified, which reduces urgency for most environments. EPSS data is absent from the input. Because Pardus is deployed in Turkish government and public sector infrastructure, successful exploitation in such environments could yield significant impact - full host compromise (C:H/I:H/A:H) from a standard user account. The narrow geographic and sector deployment footprint limits broad internet-scale risk. The reference advisory TR-CERT TR-26-1080 provides the sole public documentation; no secondary vendor or NVD CPE version details refine the affected range beyond 'before 1.0.5'.

Exploit ScenarioDerived

A low-privileged user logged into a Pardus Linux workstation launches Pardus-software or interacts with its backend service in an unintended way that triggers the incorrect privilege assignment. The user's process inherits or is granted elevated privileges - potentially root - due to the misconfigured privilege model, giving full read/write/execute access across the system. No public POC has been identified, but the low complexity (AC:L) indicates exploitation would be straightforward for an attacker with shell access.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 11, 2026

Local privilege escalation in Pardus-software (the software center for TUBITAK BILGEM's Pardus Linux distribution) allows a low-privileged local user to gain full system control. The flaw stems from incorrect privilege assignment (CWE-266), where the application grants elevated permissions to processes or objects that should operate with restricted rights, enabling an authenticated local user to escalate to root or equivalent. Versions before 1.0.5 are affected; no public exploit or active exploitation has been identified at time of analysis.

RemediationAI

Upgrade Pardus-software to version 1.0.5 or later, which is the vendor-confirmed fix version per TR-CERT advisory TR-26-1080 (https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1080). Administrators managing Pardus Linux systems should apply available system updates through the standard Pardus package management pipeline. Where immediate patching is not feasible, restrict local user access to the Pardus-software application - for example, by limiting which users may launch the software center or removing it from shared/multi-user systems - to reduce the attack surface. Monitoring for unexpected privilege escalation events or unusual process ancestry (e.g., a user process spawning a root-owned child) may help detect attempted exploitation while patching is pending.

Affected VersionsENISA

pardus-software 0 <1.0.5

Affected Packages

euvd pardus_software fix: 1.0.5

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Pardus-software is the graphical software management center bundled with Pardus Linux, a Debian-based Linux distribution developed by TUBITAK BILGEM (Scientific and Technological Research Council of Turkey - National Research Institute of Electronics and Cryptology) and deployed primarily in Turkish public sector environments. CWE-266 (Incorrect Privilege Assignment) describes a class of flaws where a software component grants a process, file, or object higher privileges than intended - for example, setting a SUID bit unnecessarily, misusing PolicyKit/sudo rules, or allowing low-privilege users to interact with a privileged backend service in a way that provides write access to protected resources. The CPE string cpe:2.3:a:tubitak_bilgem_software_technologies_research_institute:pardus-software confirms the affected product and vendor. The CVSS vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H is consistent with a local, low-complexity, no-interaction exploit yielding full-system impact without a scope change.

Know when Pardus Software gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (TR-CERT) PRIMARY HIGH
NVD 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local access required with a standard user account; low complexity once on-host; full system impact but no scope change, consistent with a privilege escalation to root.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (TR-CERT).

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Sep 11, 2026 - 16:02 EUVD
CVE Published
Sep 11, 2026 - 14:11 cve.org
HIGH 7.8

DescriptionNVD

Incorrect privilege assignment vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus-software allows Privilege Escalation.

This issue affects Pardus-software: before 1.0.5.

Executive ViewAI

Why It Matters

Pardus-software, the application distribution center for Pardus Linux, contains a local privilege escalation vulnerability allowing any authenticated local user to gain full root-level access. Organizations operating Pardus Linux systems with multiple user accounts face a critical insider threat, as employees or compromised accounts can escalate to complete system compromise. This represents material risk across confidentiality, integrity, and availability for shared or multi-tenant Pardus deployments.

Business Impact: High
Compensating Controls

Until vendor releases a patch: implement mandatory access control framework (AppArmor) restricting Pardus-software runtime capabilities; require privilege access management with multi-factor approval for su/sudo execution; enable comprehensive auditd logging with weekly manual review of escalation attempts; restrict local account creation to security team only; and isolate affected systems from critical business processes and sensitive networks.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Rare
Niche Turkish government/public-sector Linux distribution
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy