dbcve.org
Cleartext TransmissionWeakness · CWE-319

CVE-2025-8863

HIGH · 7.0 CVSS v4.0 Published 2025-08-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
79/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
YugabyteDB diagnostic information was transmitted over HTTP, which could expose sensitive data during transmission

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 · moderate confidence

YugabyteDB was transmitting diagnostic information over unencrypted HTTP connections, allowing potential network attackers to intercept sensitive operational data in transit. This represents a confidentiality breach where diagnostic endpoints lack transport encryption.

MitigationEnable TLS/HTTPS for all YugabyteDB diagnostic endpoints and ensure network communication uses encrypted channels.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify YugabyteDB processes and ports
    Run 'ps aux | grep yb' or check for processes listening on common YugabyteDB ports (13000 for web UI, 7000/7001 for master, 9000/9100 for tserver)
    Affected if YugabyteDB processes are running and listening on HTTP (not HTTPS) ports
  2. Verify diagnostic endpoint transport encryption
    Check the --use_cassandra_security_config or --use_tls flags in yb-master and yb-tserver startup scripts or configuration files; also check if ports 13000, 7000, 7001 are serving HTTP instead of HTTPS
    Affected if Diagnostic endpoints are configured to use plain HTTP without TLS encryption
  3. Inspect TLS configuration for YugabyteDB services
    Review yb-master.conf and yb-tserver.conf for 'use_tls' or 'certs_dir' settings; check if certificate files exist in the configured directory
    Affected if TLS is not enabled (use_tls=false or not set) for the master and tserver services
  4. Test network accessibility of diagnostic ports
    Use 'curl http://<host>:13000' or 'curl http://<host>:7000' to attempt access to diagnostic endpoints; also check with 'netstat -tlnp | grep -E "(13000|7000|7001)"' to confirm listening state
    Affected if HTTP requests to diagnostic ports return valid responses, confirming unencrypted access is possible
  5. Review YugabyteDB version
    Run 'yb-master --version' or 'yb-tserver --version' if available, or check the installed package version
    Affected if Installed version falls within the vulnerable range (version without TLS enforcement for diagnostics)

You are affected if YugabyteDB diagnostic endpoints are accessible over unencrypted HTTP connections without TLS/HTTPS configuration enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable TLS/HTTPS for all YugabyteDB diagnostic endpoints and ensure network communication uses encrypted channels.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8863 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8863 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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