ghinstallation returns app JWT in error responses

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.0 · CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:L

EPSS

• CVE-2022-39304: 0.39% estimated exploitation activity in the next 30 days; percentile 33.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact In ghinstallation v1, when the request to refresh an installation token failed, the HTTP request and response would be returned for debugging. https://github.com/bradleyfalzon/ghinstallation/blob/24e56b3fb7669f209134a01eff731d7e2ef72a5c/transport.go#L172-L174 The request contained the bearer JWT for the App, and was returned back to clients. This token is short lived (10 minute maximum). Patches - This has already been patched in d24f14f8be70d94129d76026e8b0f4f9170c8c3e, and is available in releases = v2.0.0. References Are there any links users can visit to find out more? - See https://docs.github.com/en/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation for the App installation flow. For more information If you have any questions or comments about this advisory: Open an issue in ghinstallation

Published by the source

19 Dec 2022, 22:48 UTC

Last modified by the source

28 Aug 2023, 22:50 UTC

Source last checked

26 Oct 2026, 14:58 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h4q8-96p6-jcgr

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

# Patch Next advisory brief: CVE-2022-39304

Advisory: ghinstallation returns app JWT in error responses
IDs: CVE-2022-39304, GHSA-h4q8-96p6-jcgr
Record: https://patchnext.com/advisories/cve-2022-39304 (revision 1, source checked 26 Oct 2026, 14:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/bradleyfalzon/ghinstallation 2.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/bradleyfalzon/ghinstallation: affected < 2.0.0; fixed in 2.0.0

## Suggested inspection (read-only)
- Go github.com/bradleyfalzon/ghinstallation: check the installed version with your package manager.

## 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 github.com/bradleyfalzon/ghinstallation.
- 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://github.com/advisories/GHSA-h4q8-96p6-jcgr (GitHub-reviewed advisory GHSA-h4q8-96p6-jcgr lists affected ranges: Go github.com/bradleyfalzon/ghinstallation >=0 <2.0.0)

Commands are suggestions: review each one before running it.