Resource Exhaustion Affecting harbor-registry-fips package, versions <3.1.2-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.38% (30th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-HARBORREGISTRYFIPS-20345071
  • published1 Oct 2026
  • disclosed16 Sept 2026

Introduced: 16 Sep 2026

NewCVE-2026-81872  (opens in a new tab)
CWE-400  (opens in a new tab)
CWE-834  (opens in a new tab)

How to fix?

Upgrade Minimos:latest harbor-registry-fips to version 3.1.2-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream harbor-registry-fips package and not the harbor-registry-fips package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.21.0, the go.opentelemetry.io/otel/sdk/log BatchingProcessor can enter a tight CPU loop when attacker-driven log emission fills its asynchronous export buffer while the exporter is backpressured. NewBatchingProcessor wraps the exporter with newBufferExporter(exporter, 1), and the poll loop calls queue.TryDequeue and bufferExporter.EnqueueExport before immediately signaling pollTrigger whenever the queue remains at or above batchSize. Because a failed nonblocking EnqueueExport leaves the queue length unchanged, the processor repeatedly retries without waiting for its ticker, exhausting CPU and degrading or denying service in the embedding process. This issue is fixed in version 0.21.0.

CVSS Base Scores

version 3.1