HAProxy known bugs for version v3.3.15 (maintenance branch 3.3) : 3

This version (3.3.15) is a release belonging to maintenance branch 3.3 whose latest version is 3.3.16. If your version is not the last one in the maintenance branch, you are missing fixes for known bugs, and by not updating you are needlessly taking the responsibility for the risk of unexpected service outages and exposing your web site to possible security issues.

The HAProxy development team takes a great care of maintaining stable versions so that all users can apply bug fixes without having to take the risk of upgrading to a new branch. In turn users are expected to apply the fixes when the development team estimates that they were worth being backported to stable branches.

Quick links

full changelog for 3.3 : here
browse history for 3.3 : here

Other versions in the same branch

This branch contains the following releases :

Date Version Comment

2026-09-28 3.3.16 ⇐ last

2026-09-24 3.3.15 ⇐ yours

2026-08-27 3.3.14

2026-07-29 3.3.13

2026-07-03 3.3.12

2026-06-26 3.3.11

2026-05-11 3.3.10

2026-05-06 3.3.9

2026-04-30 3.3.8

2026-04-23 3.3.7

2026-03-19 3.3.6

2026-03-09 3.3.5

2026-02-19 3.3.4

2026-02-12 3.3.3

2026-01-29 3.3.2

2025-12-19 3.3.1

2025-11-26 3.3.0

Date	Version	Comment
2026-09-28	3.3.16	⇐ last
2026-09-24	3.3.15	⇐ yours
2026-08-27	3.3.14
2026-07-29	3.3.13
2026-07-03	3.3.12
2026-06-26	3.3.11
2026-05-11	3.3.10
2026-05-06	3.3.9
2026-04-30	3.3.8
2026-04-23	3.3.7
2026-03-19	3.3.6
2026-03-09	3.3.5
2026-02-19	3.3.4
2026-02-12	3.3.3
2026-01-29	3.3.2
2025-12-19	3.3.1
2025-11-26	3.3.0

Known bugs affecting this version, and already fixed in the maintenance branch

These fixes have already been queued for a more recent 3.3 version. Some of them might have already been released in a more recent version than yours, and other ones might still be pending in the maintenance branch for a future release. The list may be empty if you're already on the latest version and no new fix was backported.

Bugs are almost always tagged with a severity (some people forget the severity tag when the bug is minor). The following severities are used :

MINOR: the bug presents a limited impact and can easily be mitigated ; users rarely upgrade just for these ones ;
MEDIUM: the bug can cause some undesired behaviour and may require some tricky configuration changes to avoid hitting it ; users normally upgrade to get rid of them, or temporarily disable a functionality.
MAJOR: the bug affects short term reliability and cannot easily be worked around without a significant performance penalty or without a significant functional loss ; such bugs don't stay long in the queue without a release and users must plan an upgrade as soon as possible ;
CRITICAL: this one very rarely happens ; it indicates a short-term reliability or security issue for which there is no workaround. A release will be emitted for this fix even if it's alone and users are urged to upgrade immediately. Some distro maintainers might have been informed in advance in order to agree on a coordinated release date.

Total known bugs in this version by category :

Total CRITICAL MAJOR MEDIUM MINOR

3 0 1 2 0

Total	CRITICAL	MAJOR	MEDIUM	MINOR
3	0	1	2	0

Click on the subjects below to get the full description of the bug :

Merge date Subject - Severity (minor, medium, major, critical)

2026-09-28 BUG/MEDIUM: server: skip log backend addr checks for internal proxies

2026-09-28 BUG/MEDIUM: sink: reconnect attempt not working after session lasted more than ~25 days

2026-09-28 BUG/MAJOR: mux_quic: fix potential crash on RESET_STREAM receive

Merge date	Subject - Severity (minor, medium, major, critical)
2026-09-28	BUG/MEDIUM: server: skip log backend addr checks for internal proxies
2026-09-28	BUG/MEDIUM: sink: reconnect attempt not working after session lasted more than ~25 days
2026-09-28	BUG/MAJOR: mux_quic: fix potential crash on RESET_STREAM receive

Back to the list of branches and versions
Back to the HAProxy page