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

GHSA-gfp2-w5jm-955q

MEDIUM

GHSA-gfp2-w5jm-955q is a medium-severity (CVSS 6.4) Information Exposure vulnerability in omero-web. O3 Security confirms whether GHSA-gfp2-w5jm-955q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OMERO.web exposes some unnecessary session information in the page

Also known asCVE-2021-21376PYSEC-2021-31
Published
Mar 23, 2021
Updated
Mar 13, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected
🐍omero-web

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

Description

Background

OMERO.web loads various information about the current user such as their id, name and the groups they are in, and these are available on the main webclient pages. Some additional information being loaded is not used by the webclient and is being removed in this release.

Impact

OMERO.web before 5.9.0

Patches

5.9.0

Workarounds

No workaround

References

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIomero-weball versions5.9.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

Frequently Asked Questions

### Background OMERO.web loads various information about the current user such as their id, name and the groups they are in, and these are available on the main webclient pages. Some additional information being loaded is not used by the webclient and is being removed in this release. ### Impact OMERO.web before 5.9.0 ### Patches 5.9.0 ### Workarounds No workaround ### References ### For more information If you have any questions or comments about this advisory: * Open an issue in [omero-web](https://github.com/ome/omero-web) * Email us at [security](mailto:[email protected])
O3 Security · Impact-Aware SCA

Is GHSA-gfp2-w5jm-955q in your dependencies?

O3 detects GHSA-gfp2-w5jm-955q across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.