Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

OpenRefine leaks Google API credentials in releases

GHSA-3pg4-qwc8-426r

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.openrefine:openrefine 3.8.3), 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

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.

Impact OpenRefine releases contain Google API authentication keys ("client id" and "client secret") which can be extracted from released artifacts. For instance, download the package for OpenRefine 3.8.2 on linux. It contains the file openrefine-3.8.2/webapp/extensions/gdata/module/MOD-INF/lib/openrefine-gdata.jar, which can be extracted. This archive then contains the file com/google/refine/extension/gdata/GoogleAPIExtension.java, which contains the following lines: The Base64 encoding can then be decoded to obtain the client id and client secret. Those credentials can then be used by other applications to request access to Google accounts, pretending they are OpenRefine. This assumes that they also get access to the user access tokens, which this vulnerability doesn't expose by itself. Patches The bundled credentials should be revoked. Workarounds Users should revoke access to their Google account if they have connected it to OpenRefine.

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

    Published from ghsa record GHSA-3pg4-qwc8-426r

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-3pg4-qwc8-426r

Advisory: OpenRefine leaks Google API credentials in releases
IDs: GHSA-3pg4-qwc8-426r
Record: https://patchnext.com/advisories/ghsa-3pg4-qwc8-426r (revision 1, source checked 26 Oct 2026, 16:31 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: org.openrefine:openrefine 3.8.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.openrefine:openrefine: affected < 3.8.3; fixed in 3.8.3

## Suggested inspection (read-only)
- Maven org.openrefine:openrefine: 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 org.openrefine:openrefine.
- 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-3pg4-qwc8-426r (GitHub-reviewed advisory GHSA-3pg4-qwc8-426r lists affected ranges: Maven org.openrefine:openrefine >=0 <3.8.3)

Commands are suggestions: review each one before running it.

Loading voting…