limbo.watch

In limbo for 127 days

GHSA-38jf-j9x7-jf6f

lazyown on PyPI · published in grisuno/lazyown

Read the advisory on GitHub ↗

Facts

Severity
Critical · CVSS score 9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected versions
1.0.0, release/0.2.153As entered by the maintainer. Not reviewed. Scanners can’t read this range. How to fix it
Fixed in
release/0.2.158
CVE
CVE-2026-68503 · published
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
None found in the CVE List

If you use lazyown 1.0.0, release/0.2.153

The fixed-version field says “release/0.2.158”. Check the advisory for which version fixes it. Dependabot, npm audit and OSV-Scanner won’t flag this yet.

Timeline

  1. 2026-07-08 04:48 UTC

    Published by the maintainers

    Cites CVE-2026-68503

  2. 2026-10-31 12:45 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-38jf-j9x7-jf6f.json