Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

tuf's Metadata API: Targets.get_delegated_role() is missing input validation

GHSA-77hh-43cm-v8j6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (tuf 3.1.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI tuf

    Affected
    >= 2.0.0, < 3.1.1
    Fixed in
    3.1.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

The security of both a TUF client and repository implementations depend on the concept of trusted Metadata objects verifying the signatures over other Metadata that it delegates to. This verification process uses Targets.getdelegatedrole(delegatedrole: str) to find the delegation information. tuf.api.metadata.Targets.getdelegatedrole() should ensure that the given delegatedrolename is actually a name of a role that is delegated by that Targets, but in the case of "succinct delegation" this does not happen. tuf.ngclient users are not impacted but direct users of tuf.api.metadata could be impacted. Impact If an attacker can make a Metadata API user run Targets.getdelegatedrole() so that 1. the Targets uses succinct delegation 1. the delegatedrole argument is not actually delegated by the Targets the result will be incorrect. This also means that if an attacker can make a Metadata API user run Targets.verifydelegate() or Targets.getverificationresult() so that 1. the delegating Targets…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-77hh-43cm-v8j6

  2. Revision 1 · created ·

    Published from osv record GHSA-77hh-43cm-v8j6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-77hh-43cm-v8j6

Advisory: tuf's Metadata API: Targets.get_delegated_role() is missing input validation
IDs: GHSA-77hh-43cm-v8j6
Record: https://patchnext.com/advisories/ghsa-77hh-43cm-v8j6 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tuf 3.1.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI tuf: affected >= 2.0.0, < 3.1.1; fixed in 3.1.1

## Suggested inspection (read-only)
- `python -m pip show tuf`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tuf.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-77hh-43cm-v8j6 (OSV record GHSA-77hh-43cm-v8j6 lists affected ranges: PyPI tuf >=2.0.0 <3.1.1 (fixed))
- Verified: https://github.com/advisories/GHSA-77hh-43cm-v8j6 (GitHub-reviewed advisory GHSA-77hh-43cm-v8j6 lists affected ranges: PyPI tuf >=2.0.0 <3.1.1)

Commands are suggestions: review each one before running it.

Loading voting…