CVE-2026-56747: Cribl Stream code injection in JSON Pointer-to-accessor compiler

CVE-2026-56747 · Severity: high · CVSS 8.8 · Published 2026-07-27

Cribl Stream, a data processing engine used to route and transform enterprise logs, contains a vulnerability that allows authorized users with editing permissions to run malicious code on the server. By providing specially crafted database connection details or configuration values, an attacker can gain full control over the server's operations. This could lead to the theft of sensitive data, disruption of data pipelines, or further unauthorized access to the corporate network.

Technologies: Cribl Stream. Vendors: Cribl.

Quick answers

Is CVE-2026-56747 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-56747 being exploited in the wild.
How severe is CVE-2026-56747?
High severity, with a CVSS score of 8.8, published 27 July 2026.
Which products and versions are affected?
Cribl Stream before 4.18.2.
Is there a fix for CVE-2026-56747?
A patch was published on 2026-06-24: Release date of version 4.18.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-56747 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-56747?
Check whether you run Cribl Stream at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A code injection vulnerability (CWE-94) exists in the JSON Pointer-to-accessor compiler within Cribl Stream. The flaw is rooted in improper control of code generation when processing specific configuration inputs. A remote authenticated attacker with 'edit' privileges can exploit this by submitting a crafted database connection identifier or a malicious pack configuration value. Successful exploitation allows for arbitrary JavaScript execution in the context of the server process. The issue is resolved in Cribl Stream version 4.18.2.

Affected products

  • Cribl Stream before 4.18.2

Timeline

  • 2026-06-24: patched: Release date of version 4.18.2
  • 2026-07-27: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.