OliveTin has Unauthenticated Denial of Service via Memory Exhaustion in PasswordHash API Endpoint

Exploitation

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

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-28342: 0.75% estimated exploitation activity in the next 30 days; percentile 54.99 (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.

Summary The PasswordHash API endpoint allows unauthenticated users to trigger excessive memory allocation by sending concurrent password hashing requests. By issuing multiple parallel requests, an attacker can exhaust available container memory, leading to service degradation or complete denial of service (DoS). The issue occurs because the endpoint performs computationally and memory-intensive hashing operations without request throttling, authentication requirements, or resource limits. Details The vulnerable endpoint: POST /api/olivetin.api.v1.OliveTinApiService/PasswordHash accepts a JSON body containing a password field and returns a computed password hash. Each request triggers a memory-intensive hashing operation. When multiple concurrent requests are sent, memory consumption increases significantly. There are no safeguards such as: - Authentication requirements - Rate limiting - Request throttling - Memory usage caps per request - Concurrency controls As a result, an attacker…

Published by the source

2 Mar 2026, 18:49 UTC

Last modified by the source

5 Mar 2026, 22:49 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-pc8g-78pf-4xrp

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

# Patch Next advisory brief: CVE-2026-28342

Advisory: OliveTin has Unauthenticated Denial of Service via Memory Exhaustion in PasswordHash API Endpoint
IDs: CVE-2026-28342, GHSA-pc8g-78pf-4xrp
Record: https://patchnext.com/advisories/cve-2026-28342 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/OliveTin/OliveTin 0.0.0-20260227002407-2eb5f0ba79d4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/OliveTin/OliveTin: affected < 0.0.0-20260227002407-2eb5f0ba79d4; fixed in 0.0.0-20260227002407-2eb5f0ba79d4

## Suggested inspection (read-only)
- Go github.com/OliveTin/OliveTin: 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 github.com/OliveTin/OliveTin.
- 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://github.com/advisories/GHSA-pc8g-78pf-4xrp (GitHub-reviewed advisory GHSA-pc8g-78pf-4xrp lists affected ranges: Go github.com/OliveTin/OliveTin >=0 <0.0.0-20260227002407-2eb5f0ba79d4)

Commands are suggestions: review each one before running it.