# OpenRefine leaks Google API credentials in releases Advisory record · `GHSA-3pg4-qwc8-426r` - **Identifiers:** `GHSA-3pg4-qwc8-426r` - **State:** Confirmed - **Severity:** No CVSS score - **Critical:** No - **Weakness (CWE):** [CWE-522](https://cwe.mitre.org/data/definitions/522.html) - **Tags:** [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md) - **Published:** 24 Oct 2024 - **Updated:** 4 Dec 2024 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 24 Oct 2024, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.openrefine:openrefine` (Maven): affected `<3.8.3`; fixed in `3.8.3` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > OpenRefine (Maven package org.openrefine:openrefine) versions before 3.8.3 ship Google API client ID and client secret credentials inside released artifacts, where they can be extracted from the bundled gdata extension. An attacker who extracts them could use them to request access to Google accounts while appearing to be OpenRefine, though user access tokens are not exposed by this issue. Upgrade to 3.8.3, which fixes the problem; the bundled credentials should also be revoked, and users who connected a Google account to OpenRefine should revoke that access. Written 8 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation No source has published a CVSS score for this record yet. - **CISA KEV:** Not listed. - **EPSS:** No score. ## Timeline - 31 Oct 2026, 15:12 UTC: First seen by agentprime - 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3pg4-qwc8-426r) ## Sources - [GitHub Advisory Database: GHSA-3pg4-qwc8-426r](https://github.com/advisories/GHSA-3pg4-qwc8-426r) - [OSV: GHSA-3pg4-qwc8-426r](https://osv.dev/vulnerability/GHSA-3pg4-qwc8-426r) - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .