Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.83% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-25679High confidence
Incorrect parsing of IPv6 host literals in net/url
Go standard library · net/url
7.5HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Go standard library net/url and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
7 package statesRelease-specific package status
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | go | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.25.8-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Debian trixietrixie · source | golang-1.24 | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | golang-1.19 | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | golang-1.25 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.25.8-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | golang-1.26 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.26.1-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | golang-1.26 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.26.1-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | golang-1.24 | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Open-source package ranges1 source-attributed range
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Gostdlib | SEMVER: introduced 0; fixed 1.25.8; introduced 1.26.0-0; fixed 1.26.1 | 1.25.8, 1.26.1 | OSV record ↗aggregator derived · 3 Oct 2026 |
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
url.Parse insufficiently validated the host/authority component and accepted some invalid URLs.
What
url.Parse insufficiently validated the host/authority component and accepted some invalid URLs.
Why
The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
url.Parse insufficiently validated the host/authority component and accepted some invalid URLs.
Why
The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Improper Validation of Syntactic Correctness of Input → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-1286 ↗
CWE-1286: Improper Validation of Syntactic Correctness of Input. The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- [security] Go 1.26.1 and Go 1.25.8 are released →Original publisher ↗Searchable text snapshot · Captured 27 Sep 2026Groups Groups Conversations All groups and messages Send feedback to Google Help Training Sign in Groups Groups Conversations About [security] Go 1.26.1 and Go 1.25.8 are released 5,749 views Skip to first unread message anno...@golang.org unread, Mar 6, 2026, 1:50:05 AM Mar 6 Reply to autho
04
Evidence and provenance
Published 6 Mar 2026 · Last source change 18 Sept 2026, 12:04 UTC · CWE-1286 · Improper Validation of Syntactic Correctness of Input
CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-10084
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:65838.security@golang.org ↗
- Before
- remediation: go.dev/752180 · vendor advisory: access.redhat.com/RHSA-2026:65838 · vendor advisory: pkg.go.dev/GO-2026-4601
- After
- remediation: go.dev/752180 · vendor advisory: pkg.go.dev/GO-2026-4601
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:65838.security@golang.org ↗
- Before
- remediation: go.dev/752180 · vendor advisory: pkg.go.dev/GO-2026-4601
- After
- remediation: go.dev/752180 · vendor advisory: access.redhat.com/RHSA-2026:65838 · vendor advisory: pkg.go.dev/GO-2026-4601
- Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:66401.security@golang.org ↗
- Before
- vendor advisory: access.redhat.com/RHSA-2026:66401 · vendor advisory: pkg.go.dev/GO-2026-4601
- After
- vendor advisory: pkg.go.dev/GO-2026-4601
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:66401.security@golang.org ↗
- Before
- vendor advisory: pkg.go.dev/GO-2026-4601
- After
- vendor advisory: access.redhat.com/RHSA-2026:66401 · vendor advisory: pkg.go.dev/GO-2026-4601
- Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:59830; removed vendor advisory: access.redhat.com/RHSA-2026:60018.security@golang.org ↗
- Before
- vendor advisory: access.redhat.com/RHSA-2026:59830 · vendor advisory: access.redhat.com/RHSA-2026:60018 · vendor advisory: pkg.go.dev/GO-2026-4601
- After
- vendor advisory: pkg.go.dev/GO-2026-4601
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:59830; added vendor advisory: access.redhat.com/RHSA-2026:60018.security@golang.org ↗
- Before
- vendor advisory: pkg.go.dev/GO-2026-4601
- After
- vendor advisory: access.redhat.com/RHSA-2026:59830 · vendor advisory: access.redhat.com/RHSA-2026:60018 · vendor advisory: pkg.go.dev/GO-2026-4601
- Vendor guidanceAuthoritative vendor guidance changed: added remediation: go.dev/752180.security@golang.org ↗
- Before
- vendor advisory: pkg.go.dev/GO-2026-4601
- After
- remediation: go.dev/752180 · vendor advisory: pkg.go.dev/GO-2026-4601
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- < 1.25.8; 1.26.0-0 < 1.26.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- net/url: < 1.25.8, 1.26.0-0 < 1.26.1 · Fixed: RHSA-2026:13508: Red Hat Ansible Automation Platform 2.6 for RHEL 10, Red Hat Ansible Automation Platform 2.6 for RHEL 9
- Remediation statusRemediation status changed from Awaiting fix to Patch available.security@golang.org ↗
- Before
- Awaiting fix
- After
- Patch available
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.