Is CVE-2026-56852 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-56852 being exploited in the wild.

How severe is CVE-2026-56852?

Informational severity, with a CVSS score of 0, published 21 July 2026.

Which products and versions are affected?

golang.org/x/text (Go) SEMVER:introduced=0,fixed=0.39.0.

Is there a fix for CVE-2026-56852?

Yes. golang.org/x/text (Go): upgrade to 0.39.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-56852 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-56852?

Check whether you run golang.org/x/text (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-56852: Go x/text infinite loop in unicode/norm

CVE-2026-56852 · Severity: info · CVSS 0 · Published 2026-07-21

A vulnerability exists in a Go programming library used for processing and normalizing text. When the library encounters specifically malformed or invalid text data, it can enter an infinite loop, causing the application to stop responding. This could allow an attacker to crash a service or cause a denial-of-service (DoS) by sending malicious input to an affected application.

Technologies: golang.org/x/text (Go). Vendors: Go.

Quick answers

Is CVE-2026-56852 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56852 being exploited in the wild.
How severe is CVE-2026-56852?: Informational severity, with a CVSS score of 0, published 21 July 2026.
Which products and versions are affected?: golang.org/x/text (Go) SEMVER:introduced=0,fixed=0.39.0.
Is there a fix for CVE-2026-56852?: Yes. golang.org/x/text (Go): upgrade to 0.39.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-56852 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-56852?: Check whether you run golang.org/x/text (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

golang.org/x/text (Go): upgrade to 0.39.0 or later
```
go get golang.org/x/text@v0.39.0
```

Technical details

An infinite loop vulnerability exists in the Go 'x/text/unicode/norm' package when processing invalid or truncated UTF-8 sequences. The issue resides within the norm.Iter component and affects multiple symbols including Iter.Next, Form.Span, and Form.Transform. An attacker can trigger this condition by providing specially crafted, malformed UTF-8 input to an application that uses these normalization routines, leading to a denial-of-service (DoS) through CPU exhaustion. The vulnerability is fixed in version 0.39.0 of the golang.org/x/text module.

Affected products

Go Project golang.org/x/text/unicode/norm before v0.39.0

Identifiers

CVE-2026-56852
GO-2026-5970

Timeline

2026-06-24: disclosed: Issue reported to Go project
2026-07-14: advisory: Go Vulnerability Database report published
2026-07-21: advisory: NVD record published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.