Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-93fv-4pm9-xp28

JDA (Java Discord API) downloads external URLs when updating message components

Published
Dec 9, 2025
Updated
Dec 9, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

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
EcosystemPackageVulnerable rangeFix
Mavennet.dv8tion:JDA6.0.0&&< 6.1.36.1.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.dv8tion:JDA. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-93fv-4pm9-xp28 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-93fv-4pm9-xp28. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-93fv-4pm9-xp28 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.