# CVE-2026-56748: Authenticated RCE via Symlink Following in Cribl Stream Pack Git Import

> Authenticated attackers can execute arbitrary code via symlink following in Cribl Stream's Git import feature.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-xj69-cqwc-2w67

## What is CVE-2026-56748?

CVE-2026-56748 is a high-severity path traversal vulnerability in Cribl Stream, published on 27 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper validation of symbolic links in the Pack Git import feature in Cribl Stream before 4.18.2 allows a remote authenticated attacker with Pack import and pipeline preview permissions to execute arbitrary code as the Cribl server process via a crafted Git repository containing a symbolic link in the pack's functions directory.

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following)

## Which versions are affected by CVE-2026-56748?

It affects 1 product.


Products: Cribl Cribl Stream.

## How do I fix CVE-2026-56748?

No fix has been published for CVE-2026-56748 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56748 being exploited?

There is no known exploitation of CVE-2026-56748 in the wild and no public exploit code.

## Other vulnerabilities in Cribl Stream

- [CVE-2026-56747](https://insights.sbomify.com/CVE-2026-56747/): Code Injection in JSON Pointer Processing Component in Cribl Stream (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56748 and fix it if it is affected.

What it is: CVE-2026-56748 is a high-severity path traversal vulnerability in Cribl Stream, published on 27 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56748 in the wild and no public exploit code.

Affected product: Cribl Stream. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56748/ (Markdown: https://insights.sbomify.com/CVE-2026-56748/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56748
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56748
- OSV: https://osv.dev/vulnerability/CVE-2026-56748

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56748/
Summaries are generated and may contain mistakes; the official description above is the record.