CVE-2026-10584
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedProxy server in Graph Explorer before 3.0.1 falls back to HTTP when certificate files are missing, which might allow remote threat actors to obtain sensitive information via interception of requests intended to be sent over HTTPS. To remediate this issue, users should upgrade to Graph Explorer v3.0.1 or later.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Graph Explorer proxy server has a vulnerability where it falls back to unencrypted HTTP when certificate files are missing or unavailable. This downgrade from HTTPS to HTTP exposes sensitive data in transit, allowing potential interception by remote attackers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Graph Explorer installation and versionLocate the Graph Explorer application and retrieve its version number (typically via --version flag, a version file, or package manager listing). Compare the installed version to the affected range: any version before 3.0.1 is vulnerable.Affected if The installed version is earlier than 3.0.1
-
Verify SSL/TLS certificate configurationInspect the Graph Explorer configuration files or environment for SSL certificate and key file paths. Check whether valid certificate files (.pem, .crt/.key, or similar) are present and properly referenced in the proxy configuration.Affected if Certificate files are missing, misconfigured, or the configuration references unavailable certificate paths, enabling the fallback to HTTP
-
Confirm the proxy is using HTTPSQuery the running Graph Explorer proxy service to determine the protocol in use. This can be done by checking the startup logs, configuration settings, listening ports (443 for HTTPS vs 80 for HTTP), or making a test request to the proxy endpoint.Affected if The proxy is listening on an unencrypted HTTP port (typically port 80) or traffic is flowing over HTTP instead of HTTPS
-
Inspect runtime environment for HTTP fallback behaviorReview proxy server logs or debug output for messages indicating a fallback to HTTP due to certificate unavailability. Monitor network connections from the proxy to confirm encryption is in use.Affected if Logs or network inspection reveal that the proxy has fallen back to unencrypted HTTP communication
You are affected if Graph Explorer version is earlier than 3.0.1 AND certificate files are missing or misconfigured, causing the proxy to fall back to unencrypted HTTP.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Graph Explorer to version 3.0.1 or later, which addresses the certificate fallback issue and ensures HTTPS is enforced.
Graph Explorer v3.0.1 or later
- Upgrade Graph Explorer to version 3.0.1 or later to resolve the HTTP fallback vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10584 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10584 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data