CVE-2026-55841

HIGHPre-NVD 7.57.5
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Graylog is a free and open log management platform. Prior to Graylog Server versions 6.3.12, 7.0.7, and 7.1.2 and Graylog Forwarder version 7.3, the FortiGate key-value syslog parser in graylog2-server/src/main/java/org/graylog2/inputs/codecs/GLFortiGateSyslogEvent.java and graylog2-server/src/main/java/org/graylog2/inputs/codecs/SyslogCodec.java mishandles field-like text inside quoted values. GLFortiGateSyslogEvent.getFields() uses KV_PATTERN and QUOTED_KV_PATTERN, while SyslogCodec.parse() invokes the FortiGateSyslogEvent parser; crafted values containing = or backslash-escaped quotes can cause embedded keys such as srcip, dstip, date, time, and tz to remove or overwrite original top-level fields or produce an invalid message that Graylog discards. An unauthenticated network sender who can submit syslog messages can therefore manipulate security-log fields or evade logging to obscure malicious activity. This issue is fixed in Graylog Server versions 6.3.12, 7.0.7, and 7.1.2 and Graylog Forwarder version 7.3.

CVSS v3
7.5
EG Score
7.5(low)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 28, 2026

Advisory Details (9)

Auto-updated Aug 28, 2026
Patch available. Sources: github, github_pr, github_commit.
github_commit

commit dde76d7432c4 (Graylog2/graylog2-server)

Fix landed in Graylog2/graylog2-server commit dde76d7432c4 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/commit/dde76d7432c469887d9a95c208083c5f0f73c70d
github_commit

commit d5051e604c96 (Graylog2/graylog2-server)

Fix landed in Graylog2/graylog2-server commit d5051e604c96 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/commit/d5051e604c962ef3d4e5e8e434d0ff4907d2140d
github_commit

commit 85dc699d6319 (Graylog2/graylog2-server)

Fix landed in Graylog2/graylog2-server commit 85dc699d6319 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/commit/85dc699d6319aea433583dc239077a3a799c8627
github_commit

commit 793df6e8202e (Graylog2/graylog2-server)

Fix landed in Graylog2/graylog2-server commit 793df6e8202e — awaiting tagged release

https://github.com/Graylog2/graylog2-server/commit/793df6e8202ea55c15a762e47a2a8a775961dd3f
github_pr

Fix FortiGate syslog parser handling of quoted values (`6.3`)

Fix merged in Graylog2/graylog2-server PR #26059 on 2026-05-19 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/pull/26059
github_pr

Fix FortiGate syslog parser handling of quoted values (`7.0`)

Fix merged in Graylog2/graylog2-server PR #26057 on 2026-05-19 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/pull/26057
github_pr

Fix FortiGate syslog parser handling of quoted values (`7.1`)

Fix merged in Graylog2/graylog2-server PR #26056 on 2026-05-19 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/pull/26056
github_pr

Fix FortiGate syslog parser handling of quoted values

Fix merged in Graylog2/graylog2-server PR #26050 on 2026-05-19 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/pull/26050
github Patch Available

Fortigate syslog message parser can be exploited to modify or delete fields from the original message · Advisory · Graylog2/graylog2-server · GitHub

https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-gqr6-r77p-c2pj

Vendor Advisories for CVE-2026-55841(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 4× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 23:25 UTCEG score recompute
  3. 2026-08-28 22:22 UTCEG score recompute
  4. 2026-08-28 22:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55841?
CVE-2026-55841 is a high vulnerability published on August 28, 2026. Graylog is a free and open log management platform. Prior to Graylog Server versions 6.3.12, 7.0.7, and 7.1.2 and Graylog Forwarder version 7.3, the FortiGate key-value syslog parser in graylog2-server/src/main/java/org/graylog2/inputs/codecs/GLFortiGateSyslogEvent.java and…
When was CVE-2026-55841 disclosed?
CVE-2026-55841 was first published in the National Vulnerability Database on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55841 actively exploited?
CVE-2026-55841 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.7% of all scored CVEs.
What is the CVSS score of CVE-2026-55841?
CVE-2026-55841 has a CVSS v3 base score of 7.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-55841?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55841, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55841

Explore →

Is Your Infrastructure Affected by CVE-2026-55841?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs