How severe is GHSA-93fv-4pm9-xp28?

No CVSS score has been assigned to GHSA-93fv-4pm9-xp28 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-93fv-4pm9-xp28?

GHSA-93fv-4pm9-xp28 affects the following packages: net.dv8tion:JDA (Maven). Ecosystems affected: Maven.

How do I fix GHSA-93fv-4pm9-xp28?

Update net.dv8tion:JDA to 6.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-93fv-4pm9-xp28 is resolved across your whole dependency graph.

How do I detect GHSA-93fv-4pm9-xp28 in my Maven dependencies?

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

How do I mitigate GHSA-93fv-4pm9-xp28 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-93fv-4pm9-xp28 actively exploited in the wild?

No public exploit code has been indexed for GHSA-93fv-4pm9-xp28 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.

When was GHSA-93fv-4pm9-xp28 published, and has it been updated?

GHSA-93fv-4pm9-xp28 was published on December 9, 2025 and was last updated on December 9, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

JDA (Java Discord API) downloads external URLs when updating message componentsGHSA-93fv-4pm9-xp28

Fix: discord-jda/JDA@bb6d2ce

GHSA-93fv-4pm9-xp28 is a security vulnerability in net.dv8tion:JDA. A fix is available for net.dv8tion:JDA — see the affected versions and patch details below.

Published

Dec 9, 2025

Updated

Dec 9, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 9, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕net.dv8tion:JDA

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

Description

Impact

Anyone using untrusted message components may be affected. On versions >=6.0.0,<6.1.3 of JDA, the requester will attempt to download external media URLs from components if they are used in an update or send request.

If you are used Message#getComponents or similar to get a list of components and then send those components with sendMessageComponents or other methods, you might unintentionally download media from an external URL in the resolved media of a Thumbnail, FileDisplay, or MediaGallery.

Patches

This bug has been fixed in 6.1.3, and we recommend updating.

Workarounds

Avoid sending components from untrusted messages or update to version 6.1.3.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`net.dv8tion:JDA`	≥ 6.0.0&&< 6.1.3	6.1.3`net.dv8tion:JDA:6.1.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.dv8tion:JDA, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update net.dv8tion:JDA to 6.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-93fv-4pm9-xp28 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Anyone using untrusted message components may be affected. On versions >=6.0.0,<6.1.3 of JDA, the requester will attempt to download external media URLs from components if they are used in an update or send request. If you are used `Message#getComponents` or similar to get a list of components and then send those components with `sendMessageComponents` or other methods, you might unintentionally download media from an external URL in the resolved media of a `Thumbnail`, `FileDisplay`, or `MediaGallery`. ### Patches This bug has been fixed in 6.1.3, and we recommend updating. ##

O3 Security · Impact-Aware SCA

Is GHSA-93fv-4pm9-xp28 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works