Skip to content
Fencer Intel
medium 5.8

JLSEC-2026-1388 json

Printing a `TLS.Config` exposes TLS session secrets in Reseau.jl

published 3d ago modified 1h ago

cvss
5.8
version 4.0, OSV
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Description

`Reseau.TLS.Config` keeps the server's session-ticket keys and the client's cached TLS sessions in private fields. These fields arrived with Reseau's native TLS stack in 1.1.0. Before 1.7.0, `Config` had no `show` method that left them out, so `show`, `print`, `repr`, `string` and string interpolation of a config that had handled connections printed the ticket keys' secret bytes and the cached sessions' secrets.

Reseau 1.7.0 prints only a config's public settings, and masks `key_passphrase`. `Base.dump` still prints every field of any value.

### Impact

An application that prints or logs a `TLS.Config` after it has handled connections writes these secrets to that output. Anyone who can read the output can:

- Decrypt the session tickets that a server issued while the printed ticket keys were in use. A TLS 1.2 ticket carries the session's master secret, which decrypts recorded traffic of that session and of its resumptions. A TLS 1.3 ticket carries a resumption key that lets them resume the session as the client. - Use a client's cached TLS 1.2 session secrets to decrypt recorded traffic of those sessions, and its TLS 1.3 resumption keys to resume those sessions as the client.

Reseau resumes TLS 1.3 sessions only with a new key exchange (`psk_dhe_ke`), so a TLS 1.3 secret does not decrypt recorded traffic. Session tickets are on by default.

### Patches

Fixed in Reseau 1.7.0. Upgrade to 1.7.0 or later.

### Workarounds

Don't print or log a `TLS.Config`, or any value that contains one, on an affected version. Setting `session_tickets_disabled = true` stops a server from issuing tickets. Reseau generates ticket keys at random and keeps them only in memory, so restarting a process that may have logged a config discards its ticket keys and cached sessions. Treat logs that may contain a printed config as holding secrets.

Patch / fix

Is JLSEC-2026-1388 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
OSV 4.0 5.8 CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Affected packages

ecosystem package affected fixed in
julia Reseau
>=1.1.0, <1.7.0
1.7.0

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.