Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-82288 – Unauthenticated Credential Disclosure – Stable Diffusion WebUI ≤ 1.10.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82288 is a credential disclosure vulnerability in AUTOMATIC1111’s Stable Diffusion WebUI, affecting versions through 1.10.1. The unauthenticated /sdapi/v1/cmd-flags REST API endpoint returns the application’s parsed command-line arguments in cleartext, including the credentials configured for --gradio_auth and --api_auth. An unauthenticated network attacker can use these disclosed credentials to log into the web UI, making this a high-severity issue (CVSS v4.0 8.7).

Technical details

  • Root cause: the /sdapi/v1/cmd-flags API endpoint returns all parsed command-line launch arguments without filtering sensitive values, unlike the application’s /internal/sysinfo endpoint, which does redact sensitive fields.
  • Trigger conditions: the instance is launched with --api enabled (exposing the REST API) and with --gradio-auth (and/or --api-auth) set to protect the UI/API; if --api-auth itself is not set, the REST API routes, including cmd-flags, are reachable without any authentication.
  • Attack vector: network — a remote, unauthenticated attacker sends a GET request to /sdapi/v1/cmd-flags on an internet-exposed instance.
  • Impact: disclosure of plaintext credentials (username/password) configured for Gradio and/or API authentication, which can then be used to log into the web UI or API and access application functionality without authorization.

Affected software

  • AUTOMATIC1111 stable-diffusion-webui, versions 0 through 1.10.1 (inclusive)

Severity

  • CVSS v4.0: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: no vendor-confirmed patched release has been identified at this time. Track the upstream GitHub issue (#17411) for a fix that filters credential fields out of the cmd-flags response.
  • Workarounds / network mitigations:
    • Do not expose the Stable Diffusion WebUI REST API directly to the internet; restrict access via firewall, VPN, or allow-listing to trusted hosts only.
    • If the API must be reachable remotely, always set --api-auth in addition to --gradio-auth, and use a unique, non-reused credential pair.
    • Rotate any Gradio/API credentials that may have been exposed, and audit access logs for requests to /sdapi/v1/cmd-flags.
    • Avoid launching the service with --listen on untrusted networks unless authentication and network-layer restrictions are both in place.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: stable-diffusion-webuiui-config.json, Cleanup non-default temporary directory when starting webui, API…Github…Gradio…Startup profile…Reload UI, id="txt2img_hires_fix_row1"

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge