Is CVE-2026-90507 exploited in the wild?

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

How severe is CVE-2026-90507?

Medium severity, with a CVSS score of 6.3, published 13 September 2026.

Which products and versions are affected?

Vvbbnn00 WARP-Clash-API up to commit c7bf2360073959861219b422e51ae86411051b46.

Is there a fix for CVE-2026-90507?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-90507 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-90507?

Check whether you run Vvbbnn00 WARP-Clash-API 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-90507: vvbbnn00 WARP-Clash-API improper access control in subscription handler

CVE-2026-90507 · Severity: medium · CVSS 6.3 · Published 2026-09-13

WARP-Clash-API is a subscription management tool for handling API authentication across distributed configurations. A flaw in the subscription handler embeds sensitive API credentials directly in configuration files distributed to users, causing the master API key to persist in user configs, browser history, and server logs. An attacker who obtains a leaked key gains full account takeover and complete API access.

Technologies: Vvbbnn00 WARP-Clash-API. Vendors: Vvbbnn00.

Quick answers

Is CVE-2026-90507 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-90507 being exploited in the wild.
How severe is CVE-2026-90507?: Medium severity, with a CVSS score of 6.3, published 13 September 2026.
Which products and versions are affected?: Vvbbnn00 WARP-Clash-API up to commit c7bf2360073959861219b422e51ae86411051b46.
Is there a fix for CVE-2026-90507?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-90507 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-90507?: Check whether you run Vvbbnn00 WARP-Clash-API 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.

Technical details

The vulnerability is an improper access control flaw (CWE-284) in the get_surge_subscription function of services/subscription.py. The component embeds the raw SECRET_KEY as a query parameter (key=) in distributed Surge subscription .conf files, causing the master API credential to be exposed in plaintext to end users. The attack vector is network-based with no authentication required; any user who requests a Surge subscription receives the .conf file containing the embedded credentials. An attacker who obtains the leaked key from user-side config files, proxy logs, Referer headers, or browser history can gain full API account takeover. The product is on a rolling release basis with no official version numbering, and the vendor was unresponsive to early disclosure; the product is now archived and unsupported.

Affected products

vvbbnn00 WARP-Clash-API up to commit c7bf2360073959861219b422e51ae86411051b46

Timeline

2026-07-18: disclosed
2026-09-13: advisory

References

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