Skip to main content
VulnerabilityPublished

CVE-2026-105422: TÜBİTAK BİLGEM Software Technologies Research Institute pardus-boot-repair · Path Traversal

Affects TÜBİTAK BİLGEM Software Technologies Research Institute pardus-boot-repairSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.6 Medium : upgrade to 1.1.0 when convenient.

Data as of 6 Nov 2026, 13:03 UTC

CVSS 3.1 base score
6.6Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (TR-CERT)CVSS 3.16.6
Patch
Available – fixed in 1.1.0
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade TÜBİTAK BİLGEM Software Technologies Research Institute pardus-boot-repair to 1.1.0.

Affected software

ProductAffectedFixed in
TÜBİTAK BİLGEM Software Technologies Research Institutepardus-boot-repairAffected
  • >=1.0.9 <1.1.0
Fixed in
  • 1.1.0

AI-suggested

Upgrade pardus-boot-repair to version 1.1.0 or later, where this path traversal vulnerability has been fixed. No other mitigation is required as the vendor has provided an official fix.

Description

A path traversal vulnerability (CWE-22) exists in pardus-boot-repair versions from 1.0.9 up to but not including 1.1.0, developed by TÜBİTAK BİLGEM Software Technologies Research Institute. This flaw allows an attacker to improperly access files outside the intended directory restrictions. The issue is fixed in version 1.1.0.

References

Community reviews

Loading reviews…