CVE-2026-33811

Low

fixedPATCH AVAILABLENot Available

Security vulnerability in stdlib

Description

Crash when handling long CNAME response in net

Impact Assessment

This low-severity vulnerability has limited impact but should still be addressed as part of regular security maintenance.

CVSS v3.1 Score

0.0

EPSS — Exploit Prediction

0.81%

Probability of exploitation in the next 30 days · more likely than 55.8% of all CVEs.

Quick Facts

PublishedMay 7, 2026

Last ModifiedJul 9, 2026

Discovered ByIndependent Security Researcher

Statusfixed

Attack Metrics

CVSS v3.1 Metrics Breakdown

attack Vector

attack Complexity

privileges Required

user Interaction

scope

Unchanged

confidentiality Impact

Medium

integrity Impact

Medium

availability Impact

Medium

Remediation Guide

How to Fix This Vulnerability

Remediation Steps

1Upgrade the package to version 1.26.3 or later
2Review and audit affected systems for potential exploitation
3Implement additional security controls if immediate patching is not possible
4Monitor for suspicious activity related to this vulnerability

Mitigation Strategies

Immediate Patching

High

Apply security patches to version 1.26.3 immediately

Network Segmentation

Medium

Isolate affected systems from untrusted networks until patching is complete

Monitoring and Detection

Medium

Implement enhanced monitoring for exploitation attempts and unusual behavior

Event History

Vulnerability Timeline

Vulnerability published

2026-05-07T19:21:40Z

published

Patches released: 1.26.3

2026-05-07T19:21:40Z

patched

▪ Common questions

How severe is CVE-2026-33811?

CVE-2026-33811 is rated LOW with a CVSS score of 0.

How do I fix CVE-2026-33811?

Upgrade the affected package to 1.26.3.

Back to All Vulnerabilities

CVE-2026-33811

Low

fixedPATCH AVAILABLENot Available

Security vulnerability in stdlib

ShareX LinkedIn Reddit HN

Description

Crash when handling long CNAME response in net

Impact Assessment

This low-severity vulnerability has limited impact but should still be addressed as part of regular security maintenance.

CVSS v3.1 Score

0.0

EPSS — Exploit Prediction

0.81%

Probability of exploitation in the next 30 days · more likely than 55.8% of all CVEs.

Quick Facts

PublishedMay 7, 2026

Last ModifiedJul 9, 2026

Discovered ByIndependent Security Researcher

Statusfixed

Attack Metrics

CVSS v3.1 Metrics Breakdown

attack Vector

attack Complexity

privileges Required

user Interaction

scope

Unchanged

confidentiality Impact

Medium

integrity Impact

Medium

availability Impact

Medium

Remediation Guide

How to Fix This Vulnerability

Remediation Steps

1Upgrade the package to version 1.26.3 or later
2Review and audit affected systems for potential exploitation
3Implement additional security controls if immediate patching is not possible
4Monitor for suspicious activity related to this vulnerability

Mitigation Strategies

Immediate Patching

High

Apply security patches to version 1.26.3 immediately

Network Segmentation

Medium

Isolate affected systems from untrusted networks until patching is complete

Monitoring and Detection

Medium

Implement enhanced monitoring for exploitation attempts and unusual behavior

Event History

Vulnerability Timeline

Vulnerability published

2026-05-07T19:21:40Z

published

Patches released: 1.26.3

2026-05-07T19:21:40Z

patched

▪ Common questions

How severe is CVE-2026-33811?

CVE-2026-33811 is rated LOW with a CVSS score of 0.

How do I fix CVE-2026-33811?

Upgrade the affected package to 1.26.3.

Back to All Vulnerabilities