Skip to main content

UlakPDF CVE-2026-88916

| EUVDEUVD-2026-85869 MEDIUM
Incorrect Authorization (CWE-863)
2026-09-24 TR-CERT GHSA-6gp4-g9px-6pmh
6.8
CVSS 3.1 · Vendor: TR-CERT
View

Attack ChainAIDerived

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

  1. Access
    Authenticate as low-privileged user
  2. Delivery
    Send crafted request to UlakPDF
  3. Exploit
    Bypass incorrect authorization check
  4. Execution
    Escalate to higher privileges
  5. Impact
    Read and modify protected data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an existing authenticated low-privileged account on the target UlakPDF instance (PR:L) and network reachability to its interface (AV:N). The high attack complexity (AC:H) indicates a non-default or non-trivial precondition must be met - the description does not name the specific feature, parameter, or state involved, so the exact trigger is not confirmable from available data. No user interaction is required (UI:N). The chief limiting factors are the need for prior valid credentials and the elevated attack complexity; combined with the product's narrow academic/government deployment, realistic exposure is constrained.

Impact

This is a moderate-severity issue whose real-world priority is tempered by both its CVSS composition and the affected product's limited footprint. The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N, base 6.8) describes a network-reachable but non-trivial attack (AC:H) that requires an already-authenticated low-privileged account (PR:L) and yields high confidentiality and integrity impact through privilege escalation, with no availability impact (A:N). The high AC and required prior authentication meaningfully raise the bar versus a fully unauthenticated remote flaw. There is no EPSS score, no CISA KEV listing, and no public proof-of-concept, so there is no public exploit identified at time of analysis and no evidence of active exploitation - the signals point to a genuine but not urgently-weaponized authorization defect rather than a high-priority mass-exploitation risk. SSVC-style framing is unavailable (no exploitation/automatable/technical-impact decision data was provided). Note that the input Tags label this 'Authentication Bypass' while the CWE (CWE-863 Incorrect Authorization) and description (Privilege Escalation) indicate an authorization/priv-esc flaw, not an authentication bypass - this mislabeling should be corrected. The description is sparse (no named endpoint, feature, or mechanism), so the exact escalation path is not confirmable from available data.

Exploit ScenarioDerived

An attacker who already holds a low-privileged authenticated account on an UlakPDF instance sends crafted requests that exploit an incorrect authorization check to perform actions reserved for higher-privileged users, gaining elevated access to read and modify protected data. The AC:H rating implies the attacker must satisfy some non-trivial condition (e.g., specific request state or race/parameter manipulation) rather than a single trivial request. No public exploit code is currently available.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 24, 2026

Privilege escalation in TÜBİTAK ULAKBİM UlakPDF (all versions through 09092026) allows an authenticated, low-privileged user to reach data and functionality that should be reserved for higher-privileged roles, driven by an incorrect authorization check in the application's access-control logic. The issue carries a CVSS 3.1 base score of 6.8 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N), meaning it is network-reachable but requires a pre-existing valid low-privileged account plus a non-trivial precondition that the public description does not name, and requires no user interaction; confidentiality and integrity impacts are high while availability is unaffected. Reported by TR-CERT via siberguvenlik.gov.tr, the flaw is constrained in real-world priority by the credential prerequisite, the elevated attack complexity, and UlakPDF's narrow academic and government deployment footprint - no public exploit identified at time of analysis.

RemediationAI

The available data does not identify a vendor-released patch or fixed version, so confirm current guidance with TÜBİTAK ULAKBİM and monitor the TR-CERT advisory at https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1170 for an updated build; upgrade to the first release that explicitly addresses incorrect authorization once it is named rather than assuming an unversioned latest build is fixed. Until then, the highest-value compensating control is to treat low-privileged accounts as the attack prerequisite and shrink that population: audit and disable unused accounts, avoid granting self-service registration, and rotate credentials for any account that may have been used in an escalation attempt - the trade-off is added administrative overhead and possible loss of convenience for legitimate users. Restrict network reachability to the UlakPDF interface (VPN-only access, IP allowlisting, or network segmentation) so that only authenticated and trusted clients can reach it, accepting that this reduces remote usability; note that because AC:H implies a non-default precondition, hardening the deployment toward a default, minimal configuration may remove the necessary state. Add server-side monitoring for authorization failures and for low-privileged sessions invoking privileged operations, since the product's own logs are the likeliest detection point, and keep a tested backup of the UlakPDF data store so unauthorized modifications (I:H) can be reverted. Finally, because the exact vulnerable feature is not confirmed in the available data, do not rely on blocking any single endpoint or parameter as a complete mitigation.

Affected VersionsENISA

UlakPDF 0 ≤09092026

Affected Packages

euvd ulakpdf no fix

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

The root cause is classified as CWE-863, Incorrect Authorization: the application either omits an authorization decision on a privileged operation or evaluates it against a value the requester can influence, so a lower-privileged session is treated as though it holds higher rights. UlakPDF is a Turkish PDF reader/editor distributed by TÜBİTAK ULAKBİM, and the single CPE record (cpe:2.3:a:tübi̇tak_ulakbi̇m:ulakpdf:*:*:*:*:*:*:*:*) confirms the affected component is the application itself with no version granularity supplied, the only version boundary being the vendor-stated 'through 09092026' date-style build. The CVSS composition is informative: scope is unchanged (S:U), so the escalation stays inside UlakPDF's own authorization domain rather than crossing into an OS or sandbox boundary, and availability is unaffected (A:N), indicating the abuse path is about reading and altering protected content or configuration rather than crashing or denying service. AV:N with PR:L means the attacker must already hold a legitimate low-privileged account and can then reach the vulnerable interface over the network, while AC:H signals that a non-default state, particular parameter combination, or timing/ordering condition must be satisfied - the description does not identify that trigger, so the precise vulnerable endpoint or feature cannot be confirmed from the available intelligence.

Know when Ulakpdf 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 6.8 MEDIUM
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 6.8 MEDIUM

Network-reachable authorization flaw needing an authenticated low-priv account (PR:L) and a non-trivial precondition (AC:H); priv-esc grants high C/I but no availability impact (A:N).

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

Primary rating from Vendor (TR-CERT).

CVSS VectorVendor: TR-CERT

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

DescriptionCVE.org

Incorrect Authorization vulnerability in TÜBİTAK ULAKBİM UlakPDF allows Privilege Escalation.

This issue affects UlakPDF: through 09092026.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Low
Niche PDF tool from Turkey's TÜBİTAK ULAKBİM; academic/government niche footprint
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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
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