NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2022-32149 — x/text

HIGHFix: golang/text@434eadc

CVE-2022-32149 is a high-severity (CVSS 7.5) CWE-772 vulnerability in golang.org/x/text. A fix is available for golang.org/x/text — see the affected versions and patch details below.

Denial of service via crafted Accept-Language header in golang.org/x/text/language

Also known asGHSA-69ch-w2m2-3vjpGO-2022-1059
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-32149.

EPSS Exploitation Probability

via FIRST.org ↗
1.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk
0.00%0.79%1.58%2.38%0.1%1.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹golang.org/x/text

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

The BCP 47 tag parser has quadratic time complexity due to inherent aspects of its design. Since the parser is, by design, exposed to untrusted user input, this can be leveraged to force a program to consume significant time parsing Accept-Language headers. The parser cannot be easily rewritten to fix this behavior for various reasons. Instead the solution implemented in this CL is to limit the total complexity of tags passed into ParseAcceptLanguage by limiting the number of dashes in the string to 1000. This should be more than enough for the majority of real world use cases, where the number of tags being sent is likely to be in the single digits.

Specific Go Packages Affected

golang.org/x/text/language

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogolang.org/x/textall versions0.3.8go get golang.org/x/text@v0.3.8

Affected Products

1 product · 1 configurations
Application
textgolang
< 0.3.8
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/text, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update golang.org/x/text to 0.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-32149 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

After careful analysis of the vulnerability Redhat is choosing to keep the vulnerability severity as moderate,the vulnerability exists in the ParseAcceptLanguage function of the golang text/language package,when an attacker could craft an unusually large accept header and due to the parser taking quadratic time…

ProductFixed inAdvisory
Logging subsystem for Red Hat OpenShift 5.4openshift-logging/elasticsearch-proxy-rhel8:v1.0.0-300RHSA-2022:7435
OADP-1.0-RHEL-8oadp/oadp-velero-rhel8:1.0.7-5RHSA-2023:0692
OpenShift Custom Metrics Autoscaler 2custom-metrics-autoscaler-tech-preview/custom-metrics-autoscaler-rhel8:2.8.2-143RHSA-2023:1042
OpenShift Developer Tools and Services for OCP 4.9ocp-tools-4/service-binding-operator-bundle:v1.3.1-7RHSA-2022:7407
OpenShift Logging 5.3openshift-logging/elasticsearch-proxy-rhel8:v1.0.0-302RHSA-2022:6882
Red Hat Enterprise Linux 8.6 Extended Update Supportcontainer-tools:rhel8-8060020240413110723.3b538bd8RHSA-2024:1994
Red Hat Enterprise Linux 8.8 Extended Update Supportcontainer-tools:rhel8-8080020240422101606.0f77c1b7RHSA-2024:2077
Red Hat Migration Toolkit for Containers 1.7rhmtc/openshift-migration-velero-rhel8:v1.7.7-5RHSA-2023:0693

Frequently Asked Questions

The BCP 47 tag parser has quadratic time complexity due to inherent aspects of its design. Since the parser is, by design, exposed to untrusted user input, this can be leveraged to force a program to consume significant time parsing Accept-Language headers. The parser cannot be easily rewritten to fix this behavior for various reasons. Instead the solution implemented in this CL is to limit the total complexity of tags passed into ParseAcceptLanguage by limiting the number of dashes in the string to 1000. This should be more than enough for the majority of real world use cases, where the numbe
O3 Security · Impact-Aware SCA

Is CVE-2022-32149 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2022-32149: x/text — Fixed in 0.3.8