CVE-2025-8866
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 · uneditedYugabyteDB Anywhere web server does not properly enforce authentication for the /metamaster/universe API endpoint. An unauthenticated attacker could exploit this flaw to obtain server networking configuration details, including private and public IP addresses and DNS records.
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 confidenceYugabyteDB Anywhere web server fails to enforce authentication on the /metamaster/universe API endpoint, allowing unauthenticated attackers to query and retrieve server networking configuration details including private/public IP addresses and DNS records.
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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/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:Clear
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 if YugabyteDB Anywhere is deployedReview running services and installed software to confirm YugabyteDB Anywhere is present in the environment. Check for processes listening on ports typically used by YugabyteDB Anywhere (usually 8080, 8090, or 7000).Affected if YugabyteDB Anywhere is installed and running on the system
-
Test unauthenticated access to /metamaster/universe endpointSend an HTTP GET request to http://<yugabytedb-host>:<port>/metamaster/universe without providing any authentication credentials (no Authorization header, no session cookie).Affected if The endpoint returns HTTP 200 with JSON data containing network configuration such as IP addresses or DNS records without requiring any credentials
-
Verify the response contains sensitive network detailsInspect the HTTP response body from the unauthenticated /metamaster/universe request. Look for fields that expose private IP addresses, public IP addresses, hostnames, or DNS-related information.Affected if The response includes internal networking details such as node IPs, hostnames, or DNS configuration without authentication
-
Confirm authentication is required on other endpointsTest a different API endpoint on the same YugabyteDB Anywhere server (such as /api/v1/clusters or /api/v1/hosts) without authentication to establish that authentication is enforced elsewhere.Affected if Other endpoints properly require authentication (return 401/403) while /metamaster/universe does not (returns 200 with data)
If the /metamaster/universe endpoint returns HTTP 200 with network configuration data (IPs, DNS records) without any authentication credentials, the environment is affected by this vulnerability.
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.
From vendor dataApply vendor-provided patches to enforce authentication on the /metamaster/universe endpoint, or implement network segmentation and web application firewall rules to restrict unauthorized access until a patch is available.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8866 — 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-2025-8866 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