Import of incorrectly embargoed keys could cause early publication

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact If your installation is using the export-importer service, there is potential impact. If your installation is not importing keys via the export-importer services, your installation is not impacted. In versions 0.19.1 and earlier, the export-importer service assumed that the server it was importing from had properly embargoed keys for at least 2 hours after their expiry time. There are now known instances of servers that did not properly embargo keys. This could allow allow for imported keys to be re-published before they have expired, allowing for potential replay of RPIs. Patches This is patched in v0.18.3 and all versions 0.19.2 and later. Workarounds Ensure that the servers you are importing export zip files from are not publishing keys too early. References n/a For more information If you have any questions or comments about this advisory Open an issue in exposure-notifications-server Email us at exposure-notifications-feedback@google.com

Published by the source

21 May 2021, 16:24 UTC

Last modified by the source

9 Jan 2023, 05:04 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3wxm-m9m4-cprj

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

# Patch Next advisory brief: GHSA-3wxm-m9m4-cprj

Advisory: Import of incorrectly embargoed keys could cause early publication
IDs: GHSA-3wxm-m9m4-cprj
Record: https://patchnext.com/advisories/ghsa-3wxm-m9m4-cprj (revision 1, source checked 26 Oct 2026, 14:54 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: github.com/google/exposure-notifications-server 0.19.2, 0.18.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/google/exposure-notifications-server: affected < 0.18.3; >= 0.19.0, < 0.19.2; fixed in 0.19.2, 0.18.3

## Suggested inspection (read-only)
- Go github.com/google/exposure-notifications-server: 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/google/exposure-notifications-server.
- 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-3wxm-m9m4-cprj (GitHub-reviewed advisory GHSA-3wxm-m9m4-cprj lists affected ranges: Go github.com/google/exposure-notifications-server >=0 =0.19.0 <0.19.2)

Commands are suggestions: review each one before running it.