limbo.watch
Menu

In limbo for 57 days

GHSA-8r33-hr9m-69wh

nono-proxy` component of `nono on crates.io · published in nolabs-ai/nono

Read the advisory on GitHub ↗

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

Facts

Severity
High · CVSS score 8.2CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
Package name (nono-proxy` component of `nono)
`nono-proxy` component of `nono`As entered. Doesn’t look like a valid crates.io package name, so scanners can’t match it. How to fix it
Affected versions (nono-proxy` component of `nono)
<= 0.72.0As entered by the maintainer. Not reviewed.
Fixed in (nono-proxy` component of `nono)
0.73.0
Package name (nono-proxy` component of `nono)
`nono-proxy` component of `nono`As entered. Doesn’t look like a valid crates.io package name, so scanners can’t match it. How to fix it
Affected versions (nono-proxy` component of `nono)
>=0.73.0As entered by the maintainer. Not reviewed. Scanners can’t read this range. How to fix it
Fixed in (nono-proxy` component of `nono)
Not yet
CVE
None cited by the advisory
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
None found in the CVE List

If you use nono-proxy` component of `nono <= 0.72.0

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

Timeline

  1. 2026-09-16 15:42 UTC

    Published by the maintainers

    No CVE cited

  2. 2026-10-28 08:42 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-8r33-hr9m-69wh.json