SecBoard
Zurück zur CVE-Übersicht

CVE-2026-123007

HIGH(8.1)

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

Risk Signal Score27/100 — MITTEL
  • CVSS 8.1 — Hoch

Erwähnungen (letzte 60 Tage)

Artikel

EPSS-Score

6.4%

Exploit-Wahrscheinlichkeit (30 Tage)

CVSS Score

8.1

Technische Schwere

Beschreibung

This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or potentially execute code remotely. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Erkennung & Indikatoren

Ausnutzung

In den geprüften Quellen nicht genannt

Threat-Hunting-Queries

Sentinel/Defender KQL

DeviceProcessEvents
| where FileName == "nginx.exe"
| where ProcessCommandLine contains "segmentation fault" or ProcessCommandLine contains "heap buffer overflow"

Splunk SPL

index=* sourcetype=nginx ("segmentation fault" OR "heap buffer overflow")

Sigma

title: NGINX Heap Buffer Overflow or Segmentation Fault
status: experimental
description: Detects NGINX worker process crashes due to heap buffer overflow or segmentation fault.
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Image|endswith: '\nginx.exe'
    CommandLine|contains:
      - 'segmentation fault'
      - 'heap buffer overflow'
  condition: selection

Elastic ES|QL

from process where process.executable : "*nginx.exe" and (process.args : "*segmentation fault*" or process.args : "*heap buffer overflow*")

SecBoard-generated · behavioral · requires customization — Von SecBoard erzeugt und nicht in einer Zielumgebung validiert. Vor dem Einsatz an die eigene Protokollierung anpassen.

Referenzen