LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2339: RCE in TUBITAK BILGEM's Liderahenk

Missing Authentication for Critical Function vulnerability in TUBITAK BILGEM Software Technologies Research Institute Liderahenk allows Remote Code Inclusion, Privilege Abuse, Command Injection. This issue affects Liderahenk: before 3.5.1.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-2339 affects TUBITAK BILGEM Liderahenk before version 3.5.1. A missing authentication check on a critical function could let an attacker include remote code, abuse privileges, or inject commands. The CVSS score is 7.5 high, but exploitation requires user interaction and high attack complexity.

Executive priority

Treat as a high-priority patching and exposure review item for environments using Liderahenk. The business risk is potential system compromise, but current sources do not show confirmed active exploitation. Prioritize inventory, version validation, and vendor-directed remediation.

Technical view

The issue is CWE-306, Missing Authentication for Critical Function, in Liderahenk before 3.5.1. The CVSS v3.1 vector is AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H. Public records describe possible remote code inclusion, privilege abuse, and command injection. CISA KEV status in the provided data is false.

Likely exposure

Organizations running TUBITAK BILGEM Liderahenk versions before 3.5.1 are potentially exposed. Internet reachability is not confirmed by the sources, but the CVSS vector indicates network attack surface. Exposure depends on deployment architecture and whether vulnerable functions are reachable.

Exploitation context

No cited source confirms active exploitation. The vulnerability is serious because successful exploitation can affect confidentiality, integrity, and availability. The CVSS vector indicates no privileges are required, but user interaction and high attack complexity are factors that may limit practical exploitation.

Researcher notes

The public record is concise and references Turkish government advisories, one marked broken in the supplied data. The affected-version statement says before 3.5.1, while the affected object is sparse. Avoid assuming exploit availability, affected configurations, or fixed build details beyond the cited records.

Mitigation direction

  • Identify all Liderahenk deployments and versions.
  • Upgrade Liderahenk systems below 3.5.1 per vendor guidance.
  • If upgrade timing is unclear, consult the official advisory.
  • Restrict network access to Liderahenk administration or management interfaces.
  • Monitor for unexpected command execution or privilege changes.

Validation and detection

  • Confirm installed Liderahenk version on each system.
  • Flag any instance running below version 3.5.1.
  • Review whether vulnerable services are reachable over the network.
  • Check logs for unusual remote code inclusion or command activity.
  • Verify remediation against the official advisory.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2339 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H1.65.9TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-2339Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TUBITAK BILGEM Software Technologies Research InstituteLiderahenk0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.