dbcve.org
SkywalkingApplication · Apache

CVE-2026-30778

HIGH · 7.5 CVSS v3.1 Published 2026-04-15
Fix available
A fix is available. Upgrade to 10.4.0 or later.
See remediation →
84/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
The SkyWalking OAP /debugging/config/dump endpoint may leak sensitive configuration information of MySQL/PostgreSQL. This issue affects Apache SkyWalking: from 9.7.0 through 10.3.0. Users are recommended to upgrade to version 10.4.0, which fixes the issue.

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 confidence

The SkyWalking OAP server contains a /debugging/config/dump endpoint that exposes sensitive database configuration parameters including MySQL and PostgreSQL credentials, connection strings, and other configuration details without requiring authentication. This information disclosure allows unauthenticated attackers to obtain database credentials that could be used for further compromise.

MitigationUpgrade Apache SkyWalking to version 10.4.0. If immediate upgrade is not feasible, restrict network access to the /debugging/* endpoints via firewall or reverse proxy rules to prevent unauthorized access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SkywalkingApplication
Affected:>= 9.7.0, < 10.4.0

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/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 checks

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

  1. Identify installed SkyWalking OAP version
    Check the version file or startup logs of the SkyWalking OAP server. Common locations: oap-server/docker/.env, oap-server/pom.xml, or the version printed in OAP startup logs.
    Affected if The installed version is 9.7.0 through 9.7.9, or any version 9.8.x, 9.9.x, 10.0.x, 10.1.x, 10.2.x, or 10.3.x (i.e., >= 9.7.0 and < 10.4.0)
  2. Confirm OAP server is running
    Verify the SkyWalking OAP service is active. Check process status or docker containers: `docker ps | grep skywalking` or `systemctl status skywalking-oap-server`.
    Affected if The OAP server process is running and reachable on the configured port (default 12800)
  3. Test endpoint accessibility without authentication
    Send an HTTP GET request to the /debugging/config/dump endpoint: `curl -s http://<oap-host>:12800/debugging/config/dump`. No authentication headers should be required.
    Affected if The endpoint responds with HTTP 200 and returns configuration data including database credentials, connection strings, or other sensitive parameters without requiring any auth token
  4. Check network exposure of OAP service
    Review firewall rules, reverse proxy configuration, or Kubernetes network policies to determine if the OAP port (12800 by default) is exposed to untrusted networks or the public internet.
    Affected if The OAP HTTP port is accessible from networks other than trusted administration networks, or the /debugging/ path is not blocked by a WAF or proxy rule

You are affected if the SkyWalking OAP version is 9.7.0 through 9.7.9, any 9.8.x-10.3.x version, AND the /debugging/config/dump endpoint returns sensitive configuration data without requiring authentication.

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.

dbcve · scoped
Upgrade available Upgrade to 10.4.0 or later
Fixed in 10.4.0
Interim mitigation

Upgrade Apache SkyWalking to version 10.4.0. If immediate upgrade is not feasible, restrict network access to the /debugging/* endpoints via firewall or reverse proxy rules to prevent unauthorized access.

Recommended fix High confidence

10.4.0

  1. 1. Back up your current Apache SkyWalking configuration files and any custom setups
  2. 2. Download Apache SkyWalking version 10.4.0 from the official Apache distribution repository
  3. 3. Review the release notes and migration guide for version 10.4.0 to understand any configuration changes
  4. 4. Stop the currently running SkyWalking OAP server
  5. 5. Install Apache SkyWalking 10.4.0, preserving necessary configuration files while updating to any new config format if required
  6. 6. Start the SkyWalking OAP server with version 10.4.0
  7. 7. Verify the fix by confirming the /debugging/config/dump endpoint no longer exposes MySQL/PostgreSQL credentials
Caveat Review 10.4.0 release notes for potential breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Skywalking Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30778 — 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-2026-30778 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