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

GHSA-598q-jw82-5w66

MEDIUM

InventoryGui affected by item duplication in GUIs which use GuiStorageElement

Also known asCVE-2025-62783
Published
Oct 27, 2025
Updated
Oct 27, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk11th percentile+0.19%
0.00%0.24%0.47%0.71%0.0%0.2%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected
de.themoep:inventorygui

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

Any plugin using the GuiStorageElement is impacted.

Patches

Patched with https://github.com/Phoenix616/InventoryGui/commit/27a52ef6d934a1c232e110e0010e4aa810c27029 ("backported" to 1.6.1-SNAPSHOT) Update to 1.6.2-SNAPSHOT to guarantee that it's included!

Workarounds

Don't use the GuiStorageElement in GUIs.

References

Original issue: https://github.com/Phoenix616/InventoryGui/issues/48

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavende.themoep:inventoryguiall versions1.6.2-SNAPSHOT

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for de.themoep:inventorygui. 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 de.themoep:inventorygui to 1.6.2-SNAPSHOT or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-598q-jw82-5w66 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-598q-jw82-5w66 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-598q-jw82-5w66. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Any plugin using the `GuiStorageElement` is impacted. ### Patches Patched with https://github.com/Phoenix616/InventoryGui/commit/27a52ef6d934a1c232e110e0010e4aa810c27029 ("backported" to 1.6.1-SNAPSHOT) Update to 1.6.2-SNAPSHOT to guarantee that it's included! ### Workarounds Don't use the `GuiStorageElement` in GUIs. ### References Original issue: https://github.com/Phoenix616/InventoryGui/issues/48
O3 Security · Impact-Aware SCA

Is GHSA-598q-jw82-5w66 in your dependencies?

O3 detects GHSA-598q-jw82-5w66 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.