Panic parsing crafted input in x/text/secure/precis in golang.org/x/text

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2026-56851: 0.47% estimated exploitation activity in the next 30 days; percentile 40.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The Nickname profile can panic with an out-of-bounds slice error when transforming crafted input into a short destination buffer.

Published by the source

7 Oct 2026, 14:09 UTC

Last modified by the source

20 Oct 2026, 10:42 UTC

Source last checked

23 Oct 2026, 22:04 UTC

1. Revision 1 · created · 24 Oct 2026

   Published from osv record GO-2026-6629

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-56851

Advisory: Panic parsing crafted input in x/text/secure/precis in golang.org/x/text
IDs: CVE-2026-56851
Record: https://patchnext.com/advisories/cve-2026-56851 (revision 1, source checked 23 Oct 2026, 22:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: golang.org/x/text 0.41.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go golang.org/x/text: affected < 0.41.0; fixed in 0.41.0

## Suggested inspection (read-only)
- Go golang.org/x/text: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on golang.org/x/text.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6629 (OSV record GO-2026-6629 lists affected ranges: Go golang.org/x/text >=0 <0.41.0 (fixed))

Commands are suggestions: review each one before running it.