Skip to content
AI/ML

CVE-2026-70619

8.7
High
EPSS 0.36%Patch availableAug 5, 2026

Authz bypass lets authenticated users redirect embeddings to attacker-controlled URL or delete config.

common questions

Is CVE-2026-70619 being exploited?

Not confirmed. CVE-2026-70619 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.36% probability of exploitation in the next 30 days.

How severe is CVE-2026-70619?

CVE-2026-70619 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-70619?

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

What does CVE-2026-70619 affect?

CVE-2026-70619 affects Odysseus (commits before bf325f6), Embedding backend configuration endpoints. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-70619?

Update to bf325f6 or later, enforce admin authorization, rotate keys, audit endpoints.

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

executive summary
technical analysis
affected
Odysseus (commits before bf325f6)Embedding backend configuration endpoints
impact

Authenticated non-admins can overwrite embedding backend to exfiltrate plaintext embeddings, chat/RAG/memory data, or delete config to cause embedding denial.

action required

Immediate action required

affected versions
odysseus-dev odysseus
  • affected< bf325f6b2185cb42bc5d8f5713a64aecffb766d4

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