How many CVEs have patched assert_header_block_within_max_size?

1 published CVEs changed assert_header_block_within_max_size in elixir-mint/mint, in 1 distinct patches totalling 5 changed lines, between 2026 and 2026.

What is the latest CVE that changed assert_header_block_within_max_size?

CVE-2026-59246 (Zero-length HTTP/2 CONTINUATION frames bypass Mint's header-block byte-size cap and exhaust client memory), published 2026-07-14, changed lines 2471 to 2473 of lib/mint/http2.ex.

How does assert_header_block_within_max_size compare to the rest of elixir-mint/mint?

elixir-mint/mint has 14 CVEs with a located fix in total; 1 of them changed assert_header_block_within_max_size.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

elixir-mint/mint

Function

assert_header_block_within_max_size

Name: assert_header_block_within_max_size in elixir-mint/mint: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

lib/mint/http2.ex

Last patched July 14, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

5

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

assert_header_block_within_max_size in elixir-mint/mint was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 5 lines in total.

elixir-mint/mint has 14 CVEs with a located fix in total, so 7% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed assert_header_block_within_max_size, newest first, with the lines each fix touched.

Zero-length HTTP/2 CONTINUATION frames bypass Mint's header-block byte-size cap and exhaust client memory
CVE-2026-59246 · lines 2471–2473 · +3 −2
Medium · CVSS 6.3
EPSS 0.5%2026-07-14

Get an alert when the next CVE fix lands in elixir-mint/mint, with the patched functions.

Monitor mint CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in elixir-mint/mint changed by the most CVE fixes.

decode_body4 CVEs · lib/mint/http1.ex format_error3 CVEs · lib/mint/http1.ex block2 CVEs · lib/mint/http2.ex decode2 CVEs · lib/xhttp/conn.ex add_body2 CVEs · lib/xhttp/conn.ex byte_size2 CVEs · lib/xhttp/conn.ex

All patched functions in elixir-mint/mint

Frequently asked questions

Common questions about CVE fixes to assert_header_block_within_max_size.

How many CVEs have patched assert_header_block_within_max_size?: 1 published CVEs changed assert_header_block_within_max_size in elixir-mint/mint, in 1 distinct patches totalling 5 changed lines, between 2026 and 2026.
What is the latest CVE that changed assert_header_block_within_max_size?: CVE-2026-59246 (Zero-length HTTP/2 CONTINUATION frames bypass Mint's header-block byte-size cap and exhaust client memory), published 2026-07-14, changed lines 2471 to 2473 of lib/mint/http2.ex.
How does assert_header_block_within_max_size compare to the rest of elixir-mint/mint?: elixir-mint/mint has 14 CVEs with a located fix in total; 1 of them changed assert_header_block_within_max_size.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track elixir-mint/mint CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing