CVE-2026-67348
Authenticated IDOR in Julep exposes other tenants' execution data.
Is CVE-2026-67348 being exploited?
Not confirmed. CVE-2026-67348 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.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-67348?
CVE-2026-67348 is rated High with a CVSS score of 8.6. 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-67348?
Not known from our data. No patch reference has been recorded for CVE-2026-67348, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-67348 affect?
CVE-2026-67348 affects Julep (get_execution_details endpoint), Multi-tenant Julep deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67348?
Restrict execution_id access, apply vendor patch/workaround, rotate exposed tokens, audit logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated tenant can retrieve other tenants' execution records (inputs, outputs, metadata, temporal tokens), risking data exposure and credential/token theft.
Immediate action required
- affected< 5371a620af2582868eb121e6489a8cc14836fd50
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.