Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

RUSTSEC-2026-0349: Unauthenticated ServerHello can downgrade later connections to classical key exchange

Open
#584 0 comments 0 reactions 0 assignees View on GitHub

@SergioGasquez is already working on this.

Since Oct 15, 2026.

  • #586 by @SergioGasquez — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
15/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
security

Research direction

The vulnerable dependency is rustls 0.23.45, so start with Cargo.toml and Cargo.lock to see where rustls is pulled in. Pull request #586 is already open against this issue, so check whether it bumps rustls to 0.23.46 or later before doing any work. Done means the lockfile resolves to a patched rustls and the advisory no longer shows up in a cargo audit run.

Written by the indexing model from the issue text.

Description

Unauthenticated ServerHello can downgrade later connections to classical key exchange

Details
Package rustls
Version 0.23.45
URL https://github.com/rustls/rustls/pull/3355
Date 2026-10-14
Patched versions >=0.23.46

The client recorded the server-selected key exchange group for each server
name when processing the ServerHello, before the server was authenticated.
This record is used to predict which key share to send in future ClientHellos
to that server name.

A network attacker can answer one connection attempt with a ServerHello
selecting X25519, and then close the connection. Later ClientHellos for that
name carry only an X25519 key share, while supported_groups still lists
X25519MLKEM768 first. If the genuine server accepts that share rather than
sending a HelloRetryRequest for its preferred hybrid group, the handshake
completes with classical-only key exchange and no error. This persists for as
long as the entry stays in the client's session store.

The impact is loss of post-quantum confidentiality for affected connections
("harvest now, decrypt later"). There is no key compromise and no
authentication bypass.

The following are not affected:

  • connections to servers which send a HelloRetryRequest for their preferred group,
  • clients with resumption disabled (as nothing is stored), and
  • other server names.

This behaviour is discussed in
draft-ietf-tls-key-share-prediction,
so the practical impact depends largely on server policy.

See advisory page for additional details.

Dominant language
Rust
Stars
460
Forks
37
Avg merge
2d 16h
Merged PRs (30d)
6

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from esp-rs/espup

All issues in esp-rs/espup

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.