How severe is CVE-2023-48796?

CVE-2023-48796 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-48796?

CVE-2023-48796 affects the following packages: org.apache.dolphinscheduler:dolphinscheduler (Maven), apache-dolphinscheduler (PyPI). Ecosystems affected: Maven, PyPI.

How do I fix CVE-2023-48796?

Update org.apache.dolphinscheduler:dolphinscheduler to 3.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-48796 is resolved across your whole dependency graph.

How do I detect CVE-2023-48796 in my Maven, PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.dolphinscheduler:dolphinscheduler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-48796 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2023-48796 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-48796 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-48796?

CVE-2023-48796 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 68th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-48796?

CVE-2023-48796 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-48796 published, and has it been updated?

CVE-2023-48796 was published on November 24, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2023-48796 — dolphinscheduler

HIGH

CVE-2023-48796 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.apache.dolphinscheduler:dolphinscheduler. A fix is available for org.apache.dolphinscheduler:dolphinscheduler — see the affected versions and patch details below.

Apache dolphinscheduler sensitive information disclosure

Also known asGHSA-4vvc-r4p4-qgrrPYSEC-2023-268

Published

Nov 24, 2023

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.apache.dolphinscheduler:dolphinscheduler🐍apache-dolphinscheduler

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache DolphinScheduler.

The information exposed to unauthorized actors may include sensitive data such as database credentials.

Users who can't upgrade to the fixed version can also set environment variable MANAGEMENT_ENDPOINTS_WEB_EXPOSURE_INCLUDE=health,metrics,prometheus to workaround this, or add the following section in the application.yaml file

management:
  endpoints:
    web:
      exposure:
        include: health,metrics,prometheus

This issue affects Apache DolphinScheduler: from 3.0.0 before 3.0.2.

Users are recommended to upgrade to version 3.0.2, which fixes the issue.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.dolphinscheduler:dolphinscheduler`	≥ 3.0.0&&< 3.0.2	3.0.2`org.apache.dolphinscheduler:dolphinscheduler:3.0.2`
🐍PyPI	`apache-dolphinscheduler`	≥ 3.0.0&&< 3.0.2	3.0.2`pip install --upgrade 'apache-dolphinscheduler==3.0.2'`

Affected Products

1 product · 1 configurations

Application

dolphinschedulerapache

≥ 3.0.0 && < 3.0.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.dolphinscheduler:dolphinscheduler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.dolphinscheduler:dolphinscheduler to 3.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-48796 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache DolphinScheduler. The information exposed to unauthorized actors may include sensitive data such as database credentials. Users who can't upgrade to the fixed version can also set environment variable `MANAGEMENT_ENDPOINTS_WEB_EXPOSURE_INCLUDE=health,metrics,prometheus` to workaround this, or add the following section in the `application.yaml` file ``` management: endpoints: web: exposure: include: health,metrics,prometheus ``` This issue affects Apache DolphinScheduler: from 3.0.0 before

O3 Security · Impact-Aware SCA

Is CVE-2023-48796 in your dependencies?

Find it across Maven, PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-200Information Exposure

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Nov 24, 2023

Last updated

Oct 28, 2026

Identifiers

CVE-2023-48796

GHSA-4vvc-r4p4-qgrr

PYSEC-2023-268

References

Advisorygithub.com · CVE 2023 48796.json Advisorylists.apache.org · ffrmkcwgr2lcz0f5nnnyswhpn3fytsvo Advisorynvd.nist.gov · CVE 2023 48796 Webopenwall.com Webopenwall.com Webgithub.com · PYSEC 2023 268.yaml Packagegithub.com · dolphinscheduler

Related vulnerabilities

This CVE is high severity; 6 of 8 other CVEs affecting dolphinscheduler are rated as high or higher (top: high).

CVE-2026-23902CVE-2025-62233CVE-2025-62188CVE-2024-43115CVE-2024-43166CVE-2024-30188CVE-2024-29831CVE-2023-49250

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2023-48796 — dolphinscheduler

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2023-48796 in your dependencies?