Skip to main content

Logsign SIEM EUVDEUVD-2026-88290

| CVE-2026-90926 HIGH
Code Injection (CWE-94)
2026-09-28 TR-CERT GHSA-42p2-fg6j-xpmj
8.8
CVSS 3.1 · Vendor: TR-CERT
View

Attack ChainAIDerived

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

  1. Access
    Obtain low-privilege SIEM account
  2. Delivery
    Send crafted request to injection point
  3. Exploit
    Inject code into eval/generation path
  4. Execution
    Execute arbitrary code on SIEM host
  5. Impact
    Tamper logs and pivot in environment

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

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

Exploitation Conditions

Requires a valid low-privilege authenticated account (PR:L) on a network-reachable Logsign SIEM instance running an affected version (6.4.101 up to but not including 6.4.117); no user interaction is needed (UI:N) and attack complexity is low (AC:L). Exploitation is limited by the authentication prerequisite - a fully anonymous attacker cannot trigger it without first obtaining credentials or access to the SIEM interface - and by being confined to the enumerated version window, so patched (>=6.4.117) or unaffected deployments are not at risk. The exact vulnerable feature/endpoint is not specified in the advisory data.

Impact

The vendor-style CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H = 8.8 High) describes a network-reachable, low-complexity code-injection flaw that requires only low-level authentication (PR:L) and no user interaction, yielding full confidentiality, integrity, and availability impact - consistent with the CWE-94/RCE tags. This is a genuinely serious signal because a SIEM is a high-value target holding aggregated security telemetry and often running with broad privileges, so code execution there can compromise an organization's entire detection/monitoring fabric. However, real-world urgency is tempered by missing exploitation signals: no EPSS score, no CISA KEV listing, and no public POC are present in the provided data, so there is no evidence of active exploitation or automated weaponization at time of analysis. The PR:L requirement further limits the attacker set to those already holding some valid (even low-privilege) account, making this more of a privilege-escalation-to-RCE risk than a fully anonymous internet-wide threat. Net: a legitimately high-severity, patch-worthy flaw for anyone running the affected Logsign SIEM versions, but current evidence points to it being a high-CVSS issue without confirmed in-the-wild exploitation rather than an emergency mass-exploitation event.

Exploit ScenarioDerived

An attacker with a low-privilege authenticated account on the Logsign SIEM web application submits crafted input to a vulnerable parameter that is passed into a code-generation/evaluation path, causing arbitrary code to execute on the SIEM host. Because no user interaction is needed and the attack is over the network with low complexity, the actor gains code execution and can pivot to tamper with logs, disable detections, or move laterally. No public exploit code was identified in the provided data, so exploitation would currently require independent vulnerability research.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 28, 2026

Code injection in Innotim Logsign SIEM versions 6.4.101 through 6.4.117 exposes network-reachable deployments to full compromise of confidentiality, integrity, and availability, as reflected by the CVSS 3.1 score of 8.8 and the CVE's CWE-94 classification. According to the CVSS vector (AV:N/AC:L/PR:L/UI:N), exploitation requires a valid low-privilege authenticated account on the SIEM instance, needs no user interaction, and can be carried out with low complexity - an anonymous attacker cannot trigger it without first obtaining credentials, and the risk is confined to the stated version window. No public exploit code or confirmed active exploitation was identified at time of analysis, and the specific vulnerable feature or endpoint is not disclosed in the available advisory data.

RemediationAI

Vendor-released patch: upgrade Logsign SIEM to version 6.4.117 or later, the version at which the affected range terminates; this is the primary and definitive fix, and no patched release earlier than 6.4.117 is implied by the data. Because the CVSS vector requires low-privilege authentication (PR:L) and network reachability (AV:N), the most effective compensating controls until upgrading are to restrict network access to the Logsign SIEM interface and management/API endpoints to trusted administrative networks or a VPN rather than exposing them broadly, accepting the operational trade-off that remote analysts and log forwarders may need explicit allow-listing; to review and minimize low-privilege accounts and purge stale, shared, or service credentials that could satisfy the PR:L prerequisite, which reduces attack surface but will not stop an insider or already-compromised low-privilege user; and to enable and centrally forward SIEM application and audit logs to an out-of-band collector so injected actions remain visible even if the platform's own logging is tampered with, at the cost of additional storage and monitoring overhead. Web application firewall or reverse-proxy filtering of suspicious payload patterns targeting the SIEM's configuration, parsing, or query interfaces can add friction but is signature-dependent and should not be treated as a substitute for the upgrade. No third-party patch or workaround is documented in the retrieved references; the only source is the TR-CERT advisory at https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1202, which should be consulted for any localized guidance.

Affected VersionsENISA

Logsign SIEM 6.4.101 <6.4.117

Affected Packages

euvd logsign_siem fix: 6.4.117

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 flaw is a CWE-94 Improper Control of Generation of Code ('Code Injection'), a class of defect in which externally supplied input is incorporated into dynamically generated or interpreted code without adequate neutralization, allowing the injected content to execute with the privileges of the vulnerable component. Logsign SIEM is a security information and event management platform that ingests, parses, correlates, and alerts on log and event data, and such platforms typically expose configurable parsing, rule, query, or scripting surfaces to authenticated operators; the advisory does not name the exact feature, parameter, or endpoint involved, so the injection point can only be described at the class level. The CPE record cpe:2.3:a:innotim_software,_telecommunications_and_consultancy_trade_ltd._co.:logsign_siem:*:*:*:*:*:*:*:* identifies the vendor as Innotim Software, Telecommunications and Consultancy Trade Ltd. Co. with no version binding, so version scoping must come from the advisory range rather than the CPE. Because the CVSS vector reports AV:N, AC:L, PR:L, UI:N, S:U with high C/I/A impact, successful injection is consistent with the RCE and Code Injection tags supplied by TR-CERT: a low-privilege authenticated actor reaching the interface over the network can convert the injection into arbitrary code execution within the SIEM's execution context, and the unchanged scope (S:U) indicates the impact is expected to remain within the vulnerable component's security authority rather than crossing an isolation boundary.

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

Network-reachable code injection needing a low-privilege account (PR:L) and no interaction; code execution yields full host compromise, so C/I/A:H.

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

Primary rating from Vendor (TR-CERT).

CVSS VectorVendor: TR-CERT

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

Lifecycle Timeline

2
Patch available
Sep 28, 2026 - 15:16 EUVD
CVE Published
Sep 28, 2026 - 13:47 cve.org
HIGH 8.8

DescriptionCVE.org

Improper Control of Generation of Code ('Code Injection') vulnerability in Innotim Software, Telecommunications and Consultancy Trade Ltd. Co. Logsign SIEM allows Code Injection.

This issue affects Logsign SIEM: from 6.4.101 before 6.4.117.

Executive ViewAI

Why It Matters

A code injection vulnerability in Innotim Logsign SIEM versions 6.4.101 through 6.4.117 could allow an authenticated attacker with low privileges to achieve full control over the SIEM platform, impacting confidentiality, integrity, and availability. Given that SIEM systems are central to security monitoring and often store sensitive data, a compromise could significantly hinder incident detection and response, potentially leading to broader organizational risk. Leadership should prioritize mitigation efforts to protect this critical security asset.

Business Impact: High
Compensating Controls

No vendor patch available; interim mitigations include restricting network access to the SIEM management interface, enforcing least privilege for all accounts, and monitoring for anomalous code injection activity.

Threat Intelligence Overview

EPSS Score
0.3%
Top 80% exploitable
Prevalence
Low
Niche Turkish-vendor SIEM appliance, industry-specific security tooling, limited global 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 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
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
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.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

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