VulnerabilityPublished 20 Aug 2026

CVE-2026-10584: HTTPS Fallback to HTTP in Graph Explorer

Affects graph-explorerSource AWS Security Bulletins

Compare

Not known to be exploited : upgrade to 3.0.1 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.0.1

Exploitation evidence

Disclosed: evidence found.
Public on cve.org; its publication date is not in this record
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade graph-explorer to 3.0.1.

Affected software

Product	Affected	Fixed in
npmgraph-explorer`pkg:npm/graph-explorer`Other threats	Affected >=1.1.0 <3.0.1	Fixed in 3.0.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Graph Explorer version 3.0.1; upgrading to this version fully resolves the issue. If immediate upgrade is not possible, verify that deployments serve content over HTTPS by checking the protocol in browsers or via command-line tools like curl. Ensure the HOST environment variable is set during docker runs to enable proper certificate generation. Avoid using non-default configuration directory paths when relying on automatic self-signed certificate generation. These steps help prevent fallback to HTTP and maintain encrypted communication.

Description

Bulletin ID: 2026-038-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 06/02/2026 12:15 PM PDT Description: Graph Explorer is an open source application that provides visualization and exploration of data in graph databases such as Amazon Neptune. We identified CVE-2026-10584 where, under certain circumstances, the server silently falls back to HTTP when HTTPS is enabled but certificates are unavailable, resulting in cleartext transmission of sensitive information. Impacted versions: >= 1.1.0 AND < 3.0.1 Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.

Impact

Sensitive information intended to be protected by HTTPS may be transmitted in cleartext due to fallback to HTTP, increasing the risk of interception by network attackers. The impact is limited to confidentiality exposure and does not include remote code execution or other elevated impacts. No known exploits in the wild have been reported.

Summary

Graph Explorer versions >=1.1.0 and <3.0.1 suffer from a vulnerability where, if HTTPS is enabled but the server cannot obtain valid certificates, it silently downgrades connections to HTTP. This fallback results in sensitive information being transmitted in cleartext, undermining the confidentiality guarantees of HTTPS. The issue is resolved in version 3.0.1. AWS recommends upgrading to this version or applying specific configuration workarounds to ensure HTTPS is properly enforced and certificates are correctly generated.

References

aws.amazon.com/security/security-bulletins/rss/2026-038-aws/ (opens in a new tab)

Community reviews

Loading reviews…