limbo.watch
Menu

In limbo for 38 days

GHSA-2pm6-35wv-h53j

io.quarkus:quarkus-websockets-next on Maven · published in quarkusio/quarkus

Read the advisory on GitHub ↗

Fixed in 3.33.3.3. Dependabot, npm audit and OSV-Scanner won’t flag this yet. Find it in your project

Facts

Severity
High · CVSS score 7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected versions (io.quarkus:quarkus-websockets-next)
<3.33.3.3As entered by the maintainer. Not reviewed.
Fixed in (io.quarkus:quarkus-websockets-next)
3.33.3.3
Affected versions (io.quarkus:quarkus-websockets-next)
<3.27.5.3As entered by the maintainer. Not reviewed.
Fixed in (io.quarkus:quarkus-websockets-next)
3.27.5.3
Affected versions (io.quarkus:quarkus-websockets-next)
<3.39.5As entered by the maintainer. Not reviewed.
Fixed in (io.quarkus:quarkus-websockets-next)
3.39.5
CVE
CVE-2026-87742 · published
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
None found in the CVE List

If you use io.quarkus:quarkus-websockets-next <3.33.3.3

Upgrade to 3.33.3.3 or later. Dependabot, npm audit and OSV-Scanner won’t flag this yet.

Timeline

  1. 2026-10-05 09:46 UTC

    Published by the maintainers

    Cites CVE-2026-87742

  2. 2026-10-28 08:43 UTC

    First seen by Limbowatch

    not reviewed · not in OSV

  3. Waiting

    Reviewed by GitHub

  4. Waiting

    In OSV; scanners can see it

Machine-readable record: feed/GHSA-2pm6-35wv-h53j.json