Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

GovernorCompatibilityBravo incorrect ABI encoding may lead to unexpected behavior

GHSA-m6w8-fq7v-ph4m

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@openzeppelin/contracts 4.4.2; @openzeppelin/contracts-upgradeable 4.4.2), 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 The GovernorCompatibilityBravo module may lead to the creation of governance proposals that execute function calls with incorrect arguments due to bad ABI encoding. This happens if the proposal is created using explicit function signatures, e.g. a proposal to invoke the function foo(uint256) is created as propose([target], [0], ["foo(uint256)"], ["0x00..01"]). If the function selector is provided as part of the encoded proposal data the issue is not present, e.g. the same proposal is created as propose([target], [0], ["0x2fbebd3800..01"]), where 2fbebd38 is the function selector. We've assessed the instances of this contract found on chain, and did not find any occurrence of this bug in the past. Proposal creation through Tally or OpenZeppelin Defender is not affected. The core Governor contract on its own is not affected. Patches A fix is included in version v4.4.2 of @openzeppelin/contracts and @openzeppelin/contracts-upgradeable. Workarounds Do not create proposals using…

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

    Amended from ghsa record GHSA-m6w8-fq7v-ph4m

  2. Revision 1 · created ·

    Published from osv record GHSA-m6w8-fq7v-ph4m

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-m6w8-fq7v-ph4m

Advisory: GovernorCompatibilityBravo incorrect ABI encoding may lead to unexpected behavior
IDs: GHSA-m6w8-fq7v-ph4m
Record: https://patchnext.com/advisories/ghsa-m6w8-fq7v-ph4m (revision 2, source checked 26 Oct 2026, 12:16 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: @openzeppelin/contracts 4.4.2; @openzeppelin/contracts-upgradeable 4.4.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @openzeppelin/contracts: affected >= 4.3.0, < 4.4.2; fixed in 4.4.2
- npm @openzeppelin/contracts-upgradeable: affected >= 4.3.0, < 4.4.2; fixed in 4.4.2

## Suggested inspection (read-only)
- `npm ls @openzeppelin/contracts --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @openzeppelin/contracts-upgradeable --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 @openzeppelin/contracts, @openzeppelin/contracts-upgradeable.
- 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-m6w8-fq7v-ph4m (OSV record GHSA-m6w8-fq7v-ph4m lists affected ranges: npm @openzeppelin/contracts >=4.3.0 =4.3.0 <4.4.2 (fixed))
- Verified: https://github.com/advisories/GHSA-m6w8-fq7v-ph4m (GitHub-reviewed advisory GHSA-m6w8-fq7v-ph4m lists affected ranges: npm @openzeppelin/contracts >=4.3.0 =4.3.0 <4.4.2)

Commands are suggestions: review each one before running it.

Loading voting…