ChangeIntel IT change radar
Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord
CVE-2026-123613ModerateNetworkRevised 13 Nov

Rustls 0.23.13 before 0.23.45 TLS 1.3 Handshake Encryption Level Bypass

No KEV listing collectedCVSS 5.3Fix not stated
MSRC advisory NVD CVE.org

Assessment

Severity
Moderate
CVSS base score
5.3
Impact
Not stated
Exploitation detected
Unknown: not stated by MSRC
Exploitability
Not assessed
Publicly disclosed
Unknown: not stated by MSRC
EPSS · 30-day forecast
No EPSS score collected
Customer action
Required: follow the MSRC remediation guidance
More details
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Public detection template
No Nuclei template is listed in the current collected catalog
Component
Mariner
Weakness
CWE-20: Improper Input Validation
Issued by
VulnCheck
Published
11 Nov 2026 · November 2026
Last revised
13 Nov 2026Information published.
CVSS 3.1 base metricsRed raises the risk · green lowers it
Attack vector
NetworkAV:N
Attack complexity
LowAC:L
Privileges required
NonePR:N
User interaction
NoneUI:N
Scope
UnchangedS:U
Confidentiality
LowC:L
Integrity
NoneI:N
Availability
NoneA:N

Updates that fix it

0 KBs

No KB listed

No KB update is listed in the collected MSRC record. Check the MSRC advisory for product releases and other remedies.

Affected products

Open Source Software
7 affected products
  • azl3 kata-containers 4.1.0.kata1-2 on Azure Linux 3.0
  • azl3 kata-containers 4.1.0.kata2-1 on Azure Linux 3.0
  • azl3 kata-containers-cc 3.15.0.aks0-23 on Azure Linux 3.0
  • azl3 kata-containers-cc 3.15.0.aks0-24 on Azure Linux 3.0
  • azl3 rust 1.75.0-31 on Azure Linux 3.0
  • azl3 rust 1.98.1-1 on Azure Linux 3.0
  • azl3 rust-afterburn 5.8.2-2 on Azure Linux 3.0

What changed

  1. Affected products: azl3 kata-containers 4.1.0.kata1-2 on Azure Linux 3.0, azl3 kata-containers-cc 3.15.0.aks0-23 on Azure Linux 3.0, azl3 rust 1.75.0-31 on Azure Linux 3.0, azl3 rust 1.98.1-1 on Azure Linux 3.0, azl3 rust-afterburn 5.8.2-2 on Azure Linux 3.0 → azl3 kata-containers 4.1.0.kata1-2 on Azure Linux 3.0, azl3 kata-containers 4.1.0.kata2-1 on Azure Linux 3.0, azl3 kata-containers-cc 3.15.0.aks0-23 on Azure Linux 3.0, azl3 kata-containers-cc 3.15.0.aks0-24 on Azure Linux 3.0, azl3 rust 1.75.0-31 on Azure Linux 3.0, azl3 rust 1.98.1-1 on Azure Linux 3.0, azl3 rust-afterburn 5.8.2-2 on Azure Linux 3.0
  2. Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  3. Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (10)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 14 Nov 2026 · 08:16:23 UTC Last revised12 Nov 2026 01:48 UTC → 13 Nov 2026 14:46 UTC
  2. 14 Nov 2026 · 08:16:23 UTC Affected productsazl3 kata-containers 4.1.0.kata1-2 on Azure Linux 3.0, azl3 kata-containers-cc 3.15.0.aks0-23 on Azure Linux 3.0, azl3 rust 1.75.0-31 on Azure Linux 3.0, azl3 rust 1.98.1-1 on Azure Linux 3.0, azl3 rust-afterburn 5.8.2-2 on Azure Linux 3.0 → azl3 kata-containers 4.1.0.kata1-2 on Azure Linux 3.0, azl3 kata-containers 4.1.0.kata2-1 on Azure Linux 3.0, azl3 kata-containers-cc 3.15.0.aks0-23 on Azure Linux 3.0, azl3 kata-containers-cc 3.15.0.aks0-24 on Azure Linux 3.0, azl3 rust 1.75.0-31 on Azure Linux 3.0, azl3 rust 1.98.1-1 on Azure Linux 3.0, azl3 rust-afterburn 5.8.2-2 on Azure Linux 3.0
  3. 13 Nov 2026 · 12:10:20 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  4. 13 Nov 2026 · 12:10:20 UTC Source coverage: public-exploit-codeIncomplete → Current
  5. 13 Nov 2026 · 12:10:20 UTC Source coverage: first-epssIncomplete → Current
  6. 13 Nov 2026 · 12:10:20 UTC Source coverage: msrc-cvrfIncomplete → Current
  7. 13 Nov 2026 · 11:07:20 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  8. 13 Nov 2026 · 11:07:20 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  9. 13 Nov 2026 · 11:07:20 UTC Source coverage: first-epssCurrent → Incomplete
  10. 13 Nov 2026 · 11:07:20 UTC Source coverage: msrc-cvrfCurrent → Incomplete

Explore global source statements, affected packages and advisory history for CVE-2026-123613. The catalog has a separate collection scope from Microsoft release records.

More advisories, affected versions and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and daily EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Other daily score changes remain in this history.

Advisory history

15 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

14 Nov 2026 12:57:57 UTC

Rustls from 0.23.13 before 0.23.45 accepts TLS 1.3 handshake messages at the wrong encryption level when they follow a key-changing message in the same record, because Deframer::aligned does not enforce RFC 8446 record-boundary alignment. A…

nvd · CVE-2026-123613 · Published

14 Nov 2026 11:58:47 UTC

Rustls from 0.23.13 before 0.23.45 accepts TLS 1.3 handshake messages at the wrong encryption level when they follow a key-changing message in the same record, because Deframer::aligned does not enforce RFC 8446 record-boundary alignment. A…

euvd · EUVD-2026-119372 · Published

12 Nov 2026 12:55:43 UTC

Rustls from 0.23.13 before 0.23.45 accepts TLS 1.3 handshake messages at the wrong encryption level when they follow a key-changing message in the same record, because Deframer::aligned does not enforce RFC 8446 record-boundary alignment. A…

nvd · CVE-2026-123613 · Published

12 Nov 2026 11:56:16 UTC

Rustls from 0.23.13 before 0.23.45 accepts TLS 1.3 handshake messages at the wrong encryption level when they follow a key-changing message in the same record, because Deframer::aligned does not enforce RFC 8446 record-boundary alignment. A…

euvd · EUVD-2026-119372 · Published

10 Nov 2026 19:21:22 UTC

Rustls 0.23.13 before 0.23.45 TLS 1.3 Handshake Encryption Level Bypass

cve-program · CVE-2026-123613 · Published

10 Nov 2026 11:25:58 UTC

Rustls from 0.23.13 before 0.23.45 accepts TLS 1.3 handshake messages at the wrong encryption level when they follow a key-changing message in the same record, because Deframer::aligned does not enforce RFC 8446 record-boundary alignment. A…

euvd · EUVD-2026-119372 · Published

9 Nov 2026 10:04:30 UTC

TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries

osv · RUSTSEC-2026-0285 · Published

8 Nov 2026 11:08:00 UTC

Rustls from 0.23.13 before 0.23.45 accepts TLS 1.3 handshake messages at the wrong encryption level when they follow a key-changing message in the same record, because Deframer::aligned does not enforce RFC 8446 record-boundary alignment. A…

euvd · EUVD-2026-119372 · Published

8 Nov 2026 11:07:14 UTC

Rustls from 0.23.13 before 0.23.45 accepts TLS 1.3 handshake messages at the wrong encryption level when they follow a key-changing message in the same record, because Deframer::aligned does not enforce RFC 8446 record-boundary alignment. A…

nvd · CVE-2026-123613 · Published

8 Nov 2026 11:07:08 UTC

Rustls: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries

osv · GHSA-2mjx-qc3c-rqvc · Published

8 Nov 2026 11:07:08 UTC

TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries

osv · RUSTSEC-2026-0285 · Published

8 Nov 2026 03:06:35 UTC

Rustls 0.23.13 before 0.23.45 TLS 1.3 Handshake Encryption Level Bypass

cve-program · CVE-2026-123613 · Published

27 Oct 2026 15:46:16 UTC

Rustls: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries

osv · GHSA-2mjx-qc3c-rqvc · Published

24 Oct 2026 13:19:54 UTC

Rustls: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries

osv · GHSA-2mjx-qc3c-rqvc · Published

24 Oct 2026 13:19:54 UTC

TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries

osv · RUSTSEC-2026-0285 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 18:02 UTC · 254 of 275 readable · 250 fully read · documentation 469/469 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners.