Back to search

Graylog, Inc

Graylog

See the latest tracked release, confirm when it was published, and subscribe for update emails.

Current version
Last checked: 2026-09-04

7.0.13

Release date
September 02, 2026
Security status
1 high-severity CVE tracked in the last 90 days. Current version not affected.

Source

GitHub API

Public release notes are linked for the latest stored release.

Release history

See the latest published releases stored for this product.

Version Published Notes
7.0.13 2026-09-02 Release Notes
7.0.12 2026-08-05 Release Notes
7.0.11 2026-07-23 Release Notes
7.0.10 2026-07-08 Release Notes
7.0.9 2026-07-01 Release Notes
7.0.8 2026-06-03 Release Notes
7.0.7 2026-05-20 Release Notes
7.0.6 2026-04-01 Release Notes
7.0.5 2026-03-26 Release Notes

Vulnerability tracking

versionPing monitors CVEs for this product. Matching CVEs are listed below. We only display CVEs with a CVSS score of 7.0 or higher that were published within the last 90 days.

Affected status is inferred from published affected version ranges where available. Always verify against the vendor advisory before making production decisions.

CVE Severity Published Status Summary
CVE-2026-55841 HIGH (7.5) 2026-08-28 Current versionnot affected

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.

Affected versions
  • < 6.3.12
  • >= 7.0.0-alpha.1, < 7.0.7
Show 1 more
  • >= 7.1.0-alpha.1, < 7.1.2