Is CVE-2026-114662 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114662 being exploited in the wild.

How severe is CVE-2026-114662?

High severity, with a CVSS score of 8.1, published 22 October 2026.

Which products and versions are affected?

Obot Platform Obot before 0.26.0.

How is CVE-2026-114662 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-114662?

Check whether you run Obot Platform Obot 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.

CVE-2026-114662: Obot authentication bypass in CLI login flow

CVE-2026-114662 · Severity: high · CVSS 8.1 · Published 2026-10-22

Obot is a platform for building AI agents and automations. An authentication bypass in the CLI login system allows attackers to steal API keys from users by tricking them into clicking a malicious sign-in link, granting the attacker full account takeover including access to APIs, LLM gateways, and connected services. The attack requires only that the victim click a link sent by the attacker.

Technologies: Obot Platform Obot. Vendors: Obot Platform.

Quick answers

Is CVE-2026-114662 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114662 being exploited in the wild.
How severe is CVE-2026-114662?: High severity, with a CVSS score of 8.1, published 22 October 2026.
Which products and versions are affected?: Obot Platform Obot before 0.26.0.
Is there a fix for CVE-2026-114662?: Yes: fixed in 0.26.0. Until then: If unable to upgrade immediately, block POST /api/token-request at your proxy to prevent the attack, though this also disables CLI login. After upgrading, review and delete any API keys that were not created intentionally. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114662 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-114662?: Check whether you run Obot Platform Obot 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.

How to fix

Fixed in: 0.26.0

If unable to upgrade immediately, block POST /api/token-request at your proxy to prevent the attack, though this also disables CLI login. After upgrading, review and delete any API keys that were not created intentionally.

Technical details

An unauthenticated attacker can create a token request with an attacker-chosen ID via POST /api/token-request, then trick a signed-in user into opening the login link. The client-chosen request ID and lack of authentication on key retrieval allows the attacker to fetch the resulting API key before the legitimate user. The attacker can also set the key to never expire and assign arbitrary scopes, gaining full impersonation of the victim including admin access if applicable.

Affected products

Obot Platform Obot before 0.26.0

Timeline

2026-10-06: disclosed
2026-10-22: advisory

References

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