Skip to content

docs: go-libp2p v0.49.0 + boxo v0.42.1 - #11410

Merged
lidel merged 4 commits into
masterfrom
chore/bump-libp2p-quic-go
Jul 28, 2026
Merged

docs: go-libp2p v0.49.0 + boxo v0.42.1#11410
lidel merged 4 commits into
masterfrom
chore/bump-libp2p-quic-go

Conversation

@lidel

@lidel lidel commented Jul 27, 2026

Copy link
Copy Markdown
Member

@lidel lidel changed the title fix: update go-libp2p fix: go-libp2p v0.49.0 Jul 27, 2026
@lidel lidel mentioned this pull request Jul 27, 2026
52 tasks
Picks up webtransport-go v0.11.1 and quic-go v0.60.0 through go-libp2p
v0.49.0. webtransport-go v0.11.1 fixes CVE-2026-57497, unbounded
buffering of unknown WebTransport capsules, which a peer could use to
exhaust memory on any node with WebTransport enabled. Kubo enables it
by default.

v0.11.x also speaks WebTransport draft-15, so the server answers both
the current browser handshake and the newer one Firefox is
implementing. The tradeoff is that kubo can no longer dial peers
running older go-libp2p over WebTransport. Those peers can still dial
kubo, and go-to-go connections use /quic-v1 anyway.
@lidel
lidel force-pushed the chore/bump-libp2p-quic-go branch from 49a863c to e6512bb Compare July 28, 2026 13:50
@lidel lidel self-assigned this Jul 28, 2026
Reframe the webrtc-direct and WebTransport highlights around keeping
browser retrieval working, and add the user-visible 0.49 fixes the
changelog missed:

- confirmed /webrtc-direct address dropped on the shared UDP port
- Safari 26.4+ WebTransport handshake requirement
- go-to-go WebTransport dial regression
- relay backoff after losing a working relay, two shutdown races
- quic-go HTTP/3 trailer CVE-2026-40898 in the security section
@lidel lidel changed the title fix: go-libp2p v0.49.0 fix: go-libp2p v0.49.0 + boxo v0.42.1 Jul 28, 2026
Moves the pin from a pre-release commit to the tag; the only commits
between them are boxo's own go-libp2p v0.49.0 upgrade and release
mechanics. Changelog: note the v0.42.1 fixes (IPv6 HTTP providers,
shorter /routing/v1 stale windows) and the default CAR traversal
depth cap of 1024 the gateway now inherits.
@lidel lidel changed the title fix: go-libp2p v0.49.0 + boxo v0.42.1 docs: go-libp2p v0.49.0 + boxo v0.42.1 Jul 28, 2026
…uic-go

# Conflicts:
#	docs/changelogs/v0.43.md
#	go.mod
@lidel
lidel marked this pull request as ready for review July 28, 2026 15:22
@lidel
lidel requested a review from a team as a code owner July 28, 2026 15:22
@lidel
lidel merged commit 6020ab9 into master Jul 28, 2026
24 checks passed
@lidel
lidel deleted the chore/bump-libp2p-quic-go branch July 28, 2026 15:23
lidel added a commit that referenced this pull request Jul 28, 2026
* fix: update go-libp2p to patch webtransport CVE

Picks up webtransport-go v0.11.1 and quic-go v0.60.0 through go-libp2p
v0.49.0. webtransport-go v0.11.1 fixes CVE-2026-57497, unbounded
buffering of unknown WebTransport capsules, which a peer could use to
exhaust memory on any node with WebTransport enabled. Kubo enables it
by default.

v0.11.x also speaks WebTransport draft-15, so the server answers both
the current browser handshake and the newer one Firefox is
implementing. The tradeoff is that kubo can no longer dial peers
running older go-libp2p over WebTransport. Those peers can still dial
kubo, and go-to-go connections use /quic-v1 anyway.

* docs: expand 0.43 changelog for go-libp2p 0.49

Reframe the webrtc-direct and WebTransport highlights around keeping
browser retrieval working, and add the user-visible 0.49 fixes the
changelog missed:

- confirmed /webrtc-direct address dropped on the shared UDP port
- Safari 26.4+ WebTransport handshake requirement
- go-to-go WebTransport dial regression
- relay backoff after losing a working relay, two shutdown races
- quic-go HTTP/3 trailer CVE-2026-40898 in the security section

* chore: bump boxo to v0.42.1

Moves the pin from a pre-release commit to the tag; the only commits
between them are boxo's own go-libp2p v0.49.0 upgrade and release
mechanics. Changelog: note the v0.42.1 fixes (IPv6 HTTP providers,
shorter /routing/v1 stale windows) and the default CAR traversal
depth cap of 1024 the gateway now inherits.

(cherry picked from commit 6020ab9)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant