GHSA-hc4m-q9jh-xw4j: Nono cli Nono-cli'scregistry Pack Verification Can Fail Vulnerability

MODERATE
CVSS 6.6
CWE-636
Published
Advisory Summary

GHSA-hc4m-q9jh-xw4j is a MODERATE (CVSS 6.6) nono-cli'scregistry pack verification can fail vulnerability (CWE-636: Not Failing Securely ('Failing Open')) affecting Nono cli libraries in the crates.io ecosystem. The issue involves nono-cli'scregistry pack verification can fail open when provenance metadata is absent. Remediation is available by upgrading affected packages to version 0.61.3.

GHSA-hc4m-q9jh-xw4j at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-hc4m-q9jh-xw4j
Severity MODERATE
CVSS v3.1 Base Score 6.6
CWE Classification CWE-636: Not Failing Securely ('Failing Open')
Affected Product Nono cli
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 6.6

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix GHSA-hc4m-q9jh-xw4j

To remediate this vulnerability, upgrade all affected Nono cli dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nono-cli fixed: 0.61.3
Upgrade nono-cli to 0.61.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for nono-cli

How to Check if You Are Affected

To determine whether your application is affected by GHSA-hc4m-q9jh-xw4j, inspect your project dependencies for Nono cli:

inspect dependencies for nono-cli

Analyze the terminal output to locate any version of Nono cli in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.61.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-636: Not Failing Securely ('Failing Open'), where when the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions. In Nono cli, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary Registry-installed nono packs are expected to be verified from local provenance metadata before they are used. Two files are relevant: - `~/.config/nono/packages/lockfile.json` - `~/.config/nono/packages/<namespace>/<pack>/.nono-trust.bundle` Testing shows that nono fails closed when a pack has a trust bundle but no lockfile entry. However, if the trust bundle is also absent, the same pack can load successfully. Deleting security metadata should not make a pack easier to run. ## Affected behavior Observed with `always-further/claude`: 1. Delete `~/.config/nono/packages/lockfile.json`. Result: ```text nono: Package verification failed for always-further/claude: pack 'always-further/claude' has a trust bundle but no lockfile entry - reinstall with: nono pull always-further/claude --force ``` 2. Delete `~/.config/nono/packages/always-further/claude/.nono-trust.bundle`. Result: the profile loads successfully. 3. Restore `.nono-trust.bundle` while the lockfile is still absent. Result: ```text nono: Package verification failed for always-further/claude: pack 'always-further/claude' has a trust bundle but no lockfile entry - reinstall with: nono pull always-further/claude --force ``` ## Impact If both the lockfile entry and trust bundle are absent, nono may accept an installed registry pack without artifact hash verification or provenance verification. This is especially important for pack-provided session hooks, because session hooks execute on the host outside the sandbox. A pack that contributes host-executed code should not run unless nono can verify that the code is a locked and trusted pack artifact. ## Root cause `verify_profile_packs` treats the lockfile entry as optional. Existing code fails when a trust bundle exists without a matching lockfile entry, but when the trust bundle is absent too, there is no equivalent hard failure. That creates a fail-open state: - lockfile entry missing - trust bundle missing - pack directory still present - profile can load ## Recommended fix For any registry pack selected for execution, require both: 1. A matching lockfile entry in `~/.config/nono/packages/lockfile.json`. 2. A present and valid `.nono-trust.bundle` in the installed pack directory. If either is missing, fail closed with a reinstall instruction, for example: ```text reinstall with: nono pull <namespace>/<pack> --force ``` This keeps verification monotonic: removing provenance metadata cannot downgrade a verification failure into a successful launch.

GHSA-hc4m-q9jh-xw4j Affected Nono cli Versions

1 component(s)
Fixed Versions:
0.61.3
Product / Package Ecosystem Affected Versions Fixed Version
nono-cli
crates.io
< 0.61.3
0.61.3

References

Frequently Asked Questions

What is GHSA-hc4m-q9jh-xw4j?
GHSA-hc4m-q9jh-xw4j is a security vulnerability in Nono cli involving nono-cli'scregistry pack verification can fail open when provenance metadata is absent under CWE-636: Not Failing Securely ('Failing Open').
Which Nono cli versions are affected?
Affected versions include releases prior to 0.61.3 across affected packages: nono-cli.
What version fixes GHSA-hc4m-q9jh-xw4j?
Upgrading to 0.61.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is nono-cli affected?
Yes, nono-cli is affected in releases prior to 0.61.3. Upgrade your dependency to 0.61.3 or later.
What is the CVSS score of GHSA-hc4m-q9jh-xw4j?
GHSA-hc4m-q9jh-xw4j has a CVSS v3.1 base score of 6.6 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N.
What CWE is associated with GHSA-hc4m-q9jh-xw4j?
GHSA-hc4m-q9jh-xw4j is classified under CWE-636: Not Failing Securely ('Failing Open') (When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions.).
How can I check crates.io dependencies for GHSA-hc4m-q9jh-xw4j?
Run the dependency tree command: 'inspect dependencies for nono-cli'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hc4m-q9jh-xw4j",
  "modified" : "2026-07-28T15:51:30Z",
  "published" : "2026-07-28T15:51:30Z",
  "aliases" : [ ],
  "summary" : "nono-cli'scregistry pack verification can fail open when provenance metadata is absent",
  "details" : "## Summary\n\nRegistry-installed nono packs are expected to be verified from local provenance metadata before they are used. Two files are relevant:\n\n- `~/.config/nono/packages/lockfile.json`\n- `~/.config/nono/packages/<namespace>/<pack>/.nono-trust.bundle`\n\nTesting shows that nono fails closed when a pack has a trust bundle but no lockfile entry. However, if the trust bundle is also absent, the same pack can load successfully. Deleting security metadata should not make a pack easier to run.\n\n## Affected behavior\n\nObserved with `always-further/claude`:\n\n1. Delete `~/.config/nono/packages/lockfile.json`.\n\n   Result:\n\n   ```text\n   nono: Package verification failed for always-further/claude: pack 'always-further/claude' has a trust bundle but no lockfile entry - reinstall with: nono pull always-further/claude --force\n   ```\n\n2. Delete `~/.config/nono/packages/always-further/claude/.nono-trust.bundle`.\n\n   Result: the profile loads successfully.\n\n3. Restore `.nono-trust.bundle` while the lockfile is still absent.\n\n   Result:\n\n   ```text\n   nono: Package verification failed for always-further/claude: pack 'always-further/claude' has a trust bundle but no lockfile entry - reinstall with: nono pull always-further/claude --force\n   ```\n\n## Impact\n\nIf both the lockfile entry and trust bundle are absent, nono may accept an installed registry pack without artifact hash verification or provenance verification.\n\nThis is especially important for pack-provided session hooks, because session hooks execute on the host outside the sandbox. A pack that contributes host-executed code should not run unless nono can verify that the code is a locked and trusted pack artifact.\n\n## Root cause\n\n`verify_profile_packs` treats the lockfile entry as optional. Existing code fails when a trust bundle exists without a matching lockfile entry, but when the trust bundle is absent too, there is no equivalent hard failure.\n\nThat creates a fail-open state:\n\n- lockfile entry missing\n- trust bundle missing\n- pack directory still present\n- profile can load\n\n## Recommended fix\n\nFor any registry pack selected for execution, require both:\n\n1. A matching lockfile entry in `~/.config/nono/packages/lockfile.json`.\n2. A present and valid `.nono-trust.bundle` in the installed pack directory.\n\nIf either is missing, fail closed with a reinstall instruction, for example:\n\n```text\nreinstall with: nono pull <namespace>/<pack> --force\n```\n\nThis keeps verification monotonic: removing provenance metadata cannot downgrade a verification failure into a successful launch.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "nono-cli"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.61.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.61.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/always-further/nono/security/advisories/GHSA-hc4m-q9jh-xw4j"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nolabs-ai/nono/commit/db07375031642f089d549b4f7b9abece87e39f87"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/always-further/nono"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nolabs-ai/nono/releases/tag/v0.62.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-636" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-28T15:51:30Z",
    "nvd_published_at" : null
  }
}