Skip to content
Applications

CVE-2026-56747

8.7
High
EPSS 0.37%Patch availableJul 28, 2026

Authenticated code injection in Cribl Stream allows server-side JavaScript execution

common questions

Is CVE-2026-56747 being exploited?

Not confirmed. CVE-2026-56747 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.

How severe is CVE-2026-56747?

CVE-2026-56747 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-56747?

Yes. A fix has been recorded for CVE-2026-56747. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-56747 affect?

CVE-2026-56747 affects Cribl Stream < 4.18.2, Cribl pack configurations, Database connection identifiers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-56747?

Upgrade to Cribl Stream 4.18.2+, restrict editor privileges, audit configs

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Cribl Stream < 4.18.2Cribl pack configurationsDatabase connection identifiers
impact

Authenticated attackers with edit privileges can execute arbitrary JavaScript on the server, enabling RCE, data exfiltration, or privilege escalation.

action required

Immediate action required

affected versions
Cribl Cribl Stream
  • affected< 4.18.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free