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.33% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2025-61730High confidence
Handshake messages may be processed at the incorrect encryption level in crypto/tls
Go standard library · crypto/tls
5.3MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, 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 crypto/tls 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.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Debian Security Tracker: 2 affected package states with no published fix
Distribution package intelligence
9 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.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
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.6-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | go | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.24.12-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Debian trixietrixie · source | golang-1.24 | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | golang-1.19 | Affected, no fix publishedDebian currently tracks this release as open. | 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.6-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | golang-1.21 | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | golang-1.22 | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | golang-1.23 | 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 |
| 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 |
Direct vendor intelligence
2 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2025-61730 · CSAF 2.0 · revision 25 · interimSUSE Product Security TeamCVE-2025-61730
The vendor explicitly identifies these products as affected by this CVE.
- go1.24 as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.24-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.24-openssl as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.24-openssl-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.24-openssl-race as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.24-race as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.25 as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.25-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.25-openssl as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.25-openssl-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.25-openssl-race as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.25-race as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- Summary
- During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This can cause some minor information disclosure if a network-local attacker can inject messages during the handshake.
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2025-61730 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitycrypto/tls: Handshake messages may be processed at the incorrect encryption level in crypto/tls
The vendor explicitly identifies these products as affected by this CVE.
- rhai/assisted-installer-rhel9 as a component of Assisted Installer for Red Hat OpenShift Container Platform 2
- openshift-builds/openshift-builds-waiters-rhel9 as a component of Builds for Red Hat OpenShift
- cert-manager/jetstack-cert-manager-rhel9 as a component of cert-manager Operator for Red Hat OpenShift
- compliance/openshift-compliance-operator-bundle as a component of Compliance Operator
- build-of-trustee/trustee-rhel9-operator as a component of Confidential Compute Attestation
- openshift-sandboxed-containers/osc-monitor-rhel9 as a component of Confidential Compute Attestation
- cryostat/cryostat-storage-rhel9 as a component of Cryostat 4
- custom-metrics-autoscaler/custom-metrics-autoscaler-rhel9 as a component of Custom Metric Autoscaler operator for Red Hat Openshift
- dvo/deployment-validation-rhel8-operator as a component of Deployment Validation Operator
- external-secrets-operator/external-secrets-rhel9 as a component of External Secrets Operator for Red Hat OpenShift
- edo/external-dns-rhel8 as a component of ExternalDNS Operator
- edo/external-dns-rhel9 as a component of ExternalDNS Operator
- Summary
- A TLS connection handling flaw has been discovered in the golang crypto/tls library. During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This can cause some minor information disclosure if a network-local attacker can inject messages during the handshake.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This can cause some minor information disclosure if a network-local attacker can inject messages during the handshake.
What
During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This can cause some minor information disclosure if a network-local attacker can inject messages during the handshake.
Why
The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.
What
During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This can cause some minor information disclosure if a network-local attacker can inject messages during the handshake.
Why
The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.
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 Verification of Source of a Communication Channel → obtain information outside the intended access boundary
- 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-940 ↗
CWE-940: Improper Verification of Source of a Communication Channel. The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.
- 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:L/I:N/A:NCommon 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.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- 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. - Fix availability varies by product
- Affected
- go1.24 as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.24-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.24-openssl as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.24-openssl-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.24-openssl-race as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.24-race as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.25 as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.25-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.25-openssl as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.25-openssl-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.25-openssl-race as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.25-race as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- go1.24 as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- go1.24-doc as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- go1.24-openssl as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- go1.24-openssl-doc as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- go1.24-openssl-race as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- go1.24-race as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- go1.25 as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- go1.25-doc as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- go1.25-openssl as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- go1.25-openssl-doc as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- go1.25-openssl-race as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- go1.25-race as component of SUSE Linux Enterprise Server 15 SP3-LTSS
- go1.24 as component of SUSE Linux Enterprise Server 15 SP3
- go1.24-doc as component of SUSE Linux Enterprise Server 15 SP3
- go1.24-openssl as component of SUSE Linux Enterprise Server 15 SP3
- go1.24-openssl-doc as component of SUSE Linux Enterprise Server 15 SP3
- go1.24-openssl-race as component of SUSE Linux Enterprise Server 15 SP3
- go1.24-race as component of SUSE Linux Enterprise Server 15 SP3
- and 18 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- 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.25.6 and Go 1.24.12 are released →Original publisher ↗Searchable text snapshot · Captured 28 Sep 2026Groups Groups Conversations All groups and messages Send feedback to Google Help Training Sign in Groups Groups Conversations About [security] Go 1.25.6 and Go 1.24.12 are released 4,867 views Skip to first unread message anno...@golang.org unread, Jan 15, 2026, 8:02:16 PM Jan 15 Reply to au
04
Evidence and provenance
Published 28 Jan 2026 · Last source change 2 Feb 2026, 17:28 UTC · CWE-940 · Improper Verification of Source of a Communication Channel
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-2025-206448
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- < 1.24.12; 1.25.0 < 1.25.6 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- < 1.24.12; 1.25.0 < 1.25.6 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
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.