Skip to main content

UlakPDF CVE-2026-88907

| EUVDEUVD-2026-85868 HIGH
Incorrect Authorization (CWE-863)
2026-09-24 TR-CERT GHSA-974p-3f2w-mrv2
7.4
CVSS 3.1 · Vendor: TR-CERT
View

Attack ChainAIDerived

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

  1. Access
    Reach exposed UlakPDF endpoint over network
  2. Exploit
    Craft request evading authorization check
  3. Execution
    Bypass access control (CWE-863)
  4. Impact
    Read protected documents / alter 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 network reachability to a UlakPDF instance and no authentication (PR:N), but the CVSS High attack complexity (AC:H) indicates a non-trivial precondition the attacker cannot fully control - such as a specific request/parameter combination, valid resource identifier, or state that causes the authorization check to be evaluated incorrectly (CWE-863). No user interaction is needed (UI:N). Limiting factors: the AC:H condition materially reduces reliability of exploitation, the product's small real-world footprint restricts targeting opportunity, and no patch version is confirmed in the available data, so exposure depends on the specific deployed version (any build through 09092026).

Impact

This is a genuinely notable authorization flaw but not a top-tier emergency. The CVSS 3.1 score of 7.4 (High) reflects an unauthenticated network-reachable vector (AV:N/PR:N/UI:N) with high confidentiality and integrity impact (C:H/I:H), tempered by high attack complexity (AC:H) - meaning exploitation depends on conditions not fully in the attacker's control, not a trivial one-shot request. Countervailing signals lower real-world urgency: there is no EPSS probability provided, the CVE is not in CISA KEV, and no public exploit code has been identified - so this is no public exploit identified at time of analysis, not confirmed exploitation. The affected product, TÜBİTAK ULAKBİM UlakPDF, is a niche Turkish national-institute PDF tool with a small deployment footprint, which further limits opportunistic mass-exploitation appeal even if a working exploit emerged. Note a labeling nuance: the CWE is CWE-863 (Incorrect Authorization), which is an authorization defect, while the tag and description call it 'Authentication Bypass'; the practical effect (bypassing access controls to reach protected functionality) is consistent, but defenders should treat this as broken authorization rather than a credential/login bypass. The advisory originates from TR-CERT and no independent NVD enrichment or vendor patch version is confirmed in the provided data, so affected-version boundaries beyond 'through 09092026' should be verified with the vendor.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends specially crafted requests to an internet-reachable UlakPDF instance that manipulate or evade its authorization logic, gaining access to PDF documents or processing operations that should be restricted, and potentially altering server-side content. Because the CVSS complexity is High (AC:H), the attacker likely needs a specific condition (e.g., a particular request sequence, resource identifier, or timing) to succeed. No public proof-of-concept exploit is currently available.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 24, 2026

Authentication bypass in TÜBİTAK ULAKBİM's UlakPDF allows remote unauthenticated attackers to reach functionality or data that should be protected by authorization checks, affecting builds through 09092026. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N, 7.4) indicates exploitation needs no credentials and no user interaction, but the High attack complexity means a non-trivial precondition - such as a specific request/parameter combination, a valid resource identifier, or a particular application state that causes the authorization decision to be evaluated incorrectly (CWE-863) - must be satisfied, which reduces reliability. Risk assessment: this is a genuinely notable authorization flaw but not a top-tier emergency; no confirmed actively exploited (CISA KEV) status and no public exploit identified at time of analysis, and the product's limited real-world footprint narrows targeting opportunity.

RemediationAI

No vendor-released patch identified at time of analysis - the only provided reference (TR-CERT advisory TR-26-1170 at https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1170) does not include a fixed version, so upgrades cannot be verified as remediating and monitoring that advisory for a patched build is the first action. Until a fix is confirmed, apply compensating controls: place UlakPDF behind an authenticating reverse proxy or gateway that enforces its own access control on every route, which blocks unauthenticated reachability (the PR:N path in the assessed vector) at the cost of added latency and a second identity configuration to maintain; if the product cannot sit behind such a gateway, restrict network exposure with firewall/ACL rules or a VPN so only trusted networks reach the service, accepting that this degrades legitimate remote access; and audit/disable any endpoint that returns document content or administrative state without an explicit server-side authorization check, since the CWE-863 defect means some requests are being processed when they should be refused. Trade-offs to weigh: proxy-based auth can break integrations that rely on the product's own session handling, and aggressive endpoint restriction may disable legitimate workflow features. Because exploitation requires no credentials and no user interaction (AC:H notwithstanding), log and alert on anomalous unauthenticated requests to protected paths, and treat any exposed UlakPDF instance as internet-facing risk until a vendor fix version is published.

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 CWE-863, Incorrect Authorization: the application fails to correctly enforce access-control decisions, so a request that should be rejected as unauthorized is instead processed. This is distinct from a missing authentication check in that a check exists but is evaluated incorrectly - for example, comparing the wrong subject, resource, or role, or trusting a client-supplied identifier that the server fails to bind to the authenticated context - which aligns with the assessed AC:H precondition in the CVSS vector (a specific request/parameter combination or valid resource identifier must be crafted that trips the faulty decision point). The CPE cpe:2.3:a:tübi̇tak_ulakbi̇m:ulakpdf:*:*:*:*:*:*:*:* uses a wildcard version, indicating the vendor has not published a version-scoped fix reference, and the description bounds exposure to builds 'through 09092026' (a build/date designation), meaning every release up to that build is presumed affected. Because UlakPDF is a document/PDF handling platform operated by TÜBİTAK ULAKBİM (the Turkish academic network and national research infrastructure), the confidentiality and integrity impact of a bypass (C:H/I:H) is significant within deployments where the service fronts stored documents or administrative functions, though availability is unaffected (A:N). No EPSS score, KEV listing, or public proof-of-concept was provided in the source data.

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 7.4 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 7.4 HIGH

Unauthenticated network authorization bypass (AV:N/PR:N) with a non-trivial precondition (AC:H) yielding document read and modification (C:H/I:H); no availability impact and no scope change.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:N/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
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

DescriptionCVE.org

Incorrect Authorization vulnerability in TÜBİTAK ULAKBİM UlakPDF allows Authentication Bypass.

This issue affects UlakPDF: through 09092026.

Executive ViewAI

Why It Matters

UlakPDF builds through 09092026 contain an unauthenticated authorization bypass that could let remote attackers reach protected functionality or data. Although no public exploit identified at time of analysis and high attack complexity reduces reliability, the absence of a vendor patch leaves affected document workflows dependent on interim controls. Leadership should prioritize inventory and mitigation because successful exploitation could affect the confidentiality and integrity of PDF-handling resources.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis; restrict network exposure to UlakPDF, enforce authentication and authorization at an upstream proxy, apply WAF/virtual patching, monitor logs for anomalous access, and contact TÜBİTAK ULAKBİM for remediation timeline.

Threat Intelligence Overview

EPSS Score
0.3%
Top 78% exploitable
Prevalence
Low
niche Turkish national-institute PDF tool, minimal enterprise 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 HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
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
Open
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

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

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

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