What is the CVSS score of CVE-2026-14459?

CVE-2026-14459 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Pardus Software CVE-2026-14459

Q: Which versions of Pardus Software are affected by CVE-2026-14459?

Turkish Pardus Linux distributions running pardus-software version 1.0.4 and earlier contain a high-severity local privilege escalation vulnerability allowing system users to gain complete host…. A patch is available.

Q: How to fix or mitigate CVE-2026-14459?

24 hours: Inventory systems running pardus-software version 1.0.4 or earlier; prioritize systems with multiple local user accounts. 7 days: Deploy pardus-software version 1.0.5 across all affected Pardus Linux systems and confirm completion in asset management system. 30 days: Verify 100% patch compliance through automated scanning and audit local account provisioning policies.

EUVD-2026-41550 HIGH

Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') (CWE-88)

2026-07-03 TR-CERT

GHSA-rrqp-52wf-rr49

Code Injection Pardus Software Tubitak Bilgem Software Technologies Research Institute

8.8

CVSS 3.1 · Vendor: TR-CERT

View

Vulnerability Assessment

Weakness

CWE

CWE-88

OWASP Top 10:2025

A05:2025 - Injection

ASVS 5.0

V1 - Encoding and Sanitization Argument sanitization

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Jul 03, 2026

Local privilege escalation via argument injection in TUBITAK BILGEM's pardus-software (the software-center application for the Turkish Pardus Linux distribution) affects all versions up to and including 1.0.4. A low-privileged local user can smuggle attacker-controlled argument delimiters into a command the application invokes with elevated privileges, yielding full compromise of the host (confidentiality, integrity, and availability all high) with no user interaction. No public exploit has been identified at time of analysis, and the issue is not on CISA KEV; it is fixed in version 1.0.5.

Affected VersionsENISA

pardus-software ≤ 1.0.4 <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.

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

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (TR-CERT) PRIMARY 8.8 HIGH

AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Primary rating from Vendor (TR-CERT) · only source for this CVE.

CVSS VectorVendor: TR-CERT

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch available

Jul 03, 2026 - 16:01 EUVD

DescriptionCVE.org

Improper neutralization of argument delimiters in a command ('argument injection') vulnerability in TUBITAK BILGEM Software Technologies Research Institute pardus-software allows Argument Injection.

This issue affects pardus-software: from <= 1.0.4 before 1.0.5.

Executive ViewAI

Why It Matters

Turkish Pardus Linux distributions running pardus-software version 1.0.4 and earlier contain a high-severity local privilege escalation vulnerability allowing system users to gain complete host control without additional user interaction. Organizations operating Pardus Linux in environments with local user accounts face risk of full system compromise affecting confidentiality, integrity, and availability. Vendor patch to version 1.0.5 is available and must be deployed immediately.

Recommended Action

24 hours: Inventory systems running pardus-software version 1.0.4 or earlier; prioritize systems with multiple local user accounts. 7 days: Deploy pardus-software version 1.0.5 across all affected Pardus Linux systems and confirm completion in asset management system. 30 days: Verify 100% patch compliance through automated scanning and audit local account provisioning policies.

Business Impact: High

Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score

0.2%

Top 90% exploitable

Social Media

Sightings

Data Quality

6 sources

Confidence: High

EUVD

NVD

CVE.org

EPSS

Vulnrichment CIRCL

VulDB

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.2%

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

Scheduled

Exploitation

None

System Exposure· derived

Small

Automatable

Human Impact

High

Technical Impact

Total

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +44

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.