Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Out-of-bounds read and panic in ReadDir in github.com/cloudsoda/go-smb2 and github.com/hirochachacha/go-smb2

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/cloudsoda/go-smb2

    Affected
    < 0.0.0-20260609183447-7b96c35f5f4b
    Fixed in
    0.0.0-20260609183447-7b96c35f5f4b

  • Go github.com/hirochachacha/go-smb2

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

ReadDir and ReadDirPlus parse the QUERY_DIRECTORY SMB response by advancing through entries using the server-supplied NextEntryOffset field. The pre-fix code does not bound next against the remaining buffer before re-slicing, and the entry decoder IsInvalid check performs length arithmetic in int after narrowing from uint16. A guest or anonymous directory listing against an attacker-controlled or man-in-the-middle SMB server crashes the Go client process with a runtime panic when the response contains an entry whose NextEntryOffset is larger than the remaining buffer, or whose declared FileNameLength produces a length that does not match the actual buffer size.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record GO-2026-5051

Agent brief

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

# Patch Next advisory brief: go-2026-5051

Advisory: Out-of-bounds read and panic in ReadDir in github.com/cloudsoda/go-smb2 and github.com/hirochachacha/go-smb2
IDs: go-2026-5051
Record: https://patchnext.com/advisories/go-2026-5051 (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: Partial vendor fix; fixed versions by package: github.com/cloudsoda/go-smb2 0.0.0-20260609183447-7b96c35f5f4b. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cloudsoda/go-smb2: affected < 0.0.0-20260609183447-7b96c35f5f4b; fixed in 0.0.0-20260609183447-7b96c35f5f4b
- Go github.com/hirochachacha/go-smb2: affected every version

## Suggested inspection (read-only)
- Go github.com/cloudsoda/go-smb2: check the installed version with your package manager.
- Go github.com/hirochachacha/go-smb2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cloudsoda/go-smb2, github.com/hirochachacha/go-smb2.
- 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-5051 (OSV record GO-2026-5051 lists affected ranges: Go github.com/cloudsoda/go-smb2 >=0 =0)

Commands are suggestions: review each one before running it.

Loading voting…