Zebra Address Book Aborted by IPv4-Mapped Mempool Misbehavior Update

Exploitation

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

CVSS

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

EPSS

• CVE-2026-52829: 0.61% estimated exploitation activity in the next 30 days; percentile 49.23 (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.

Am I affected You are affected if: 1. You run zebrad up to and including v4.4.1. 2. Your node listens on the default [::] address on a Linux host (the standard deployment configuration — net.ipv6.bindv6only=0 is the default on all common Linux distributions). 3. Your node is synced near the chain tip (the expected production state for any node participating in the network). Summary An address normalization mismatch between the handshake path and the mempool misbehavior path causes a deterministic assertion panic when a peer connects via IPv4 to a dual-stack IPv6 listener and then triggers a mempool misbehavior penalty. The handshake path canonicalizes IPv4-mapped IPv6 addresses to plain IPv4 when storing the peer in the address book via MetaAddr::newconnected. The mempool misbehavior path forwards the raw transient socket address (IPv4-mapped IPv6 form) when sending MetaAddrChange::UpdateMisbehavior to the address book. The address book looks up the canonical IPv4 entry but then…

Published by the source

2 Jul 2026, 20:26 UTC

Last modified by the source

2 Jul 2026, 20:26 UTC

Source last checked

26 Oct 2026, 15:42 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-63wg-wjjj-7cp8

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

# Patch Next advisory brief: CVE-2026-52829

Advisory: Zebra Address Book Aborted by IPv4-Mapped Mempool Misbehavior Update
IDs: CVE-2026-52829, GHSA-63wg-wjjj-7cp8
Record: https://patchnext.com/advisories/cve-2026-52829 (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: zebra-network 7.0.0; zebrad 4.5.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io zebra-network: affected <= 6.0.0; fixed in 7.0.0
- crates.io zebrad: affected <= 4.4.1; fixed in 4.5.0

## Suggested inspection (read-only)
- crates.io zebra-network: check the installed version with your package manager.
- crates.io zebrad: 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 zebra-network, zebrad.
- 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-63wg-wjjj-7cp8 (GitHub-reviewed advisory GHSA-63wg-wjjj-7cp8 lists affected ranges: crates.io zebra-network >=0 =0 <=4.4.1)

Commands are suggestions: review each one before running it.