CVE-2026-28342

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 can repeatedly invoke the endpoint in parallel, causing excessive RAM allocation inside the container.

In a test environment, 50 concurrent requests resulted in approximately 3.2 GB of memory usage (≈64 MB per request), leading to service instability.

This behavior allows unauthenticated attackers to perform a denial of service attack by exhausting server memory resources.

PoC

Environment

• Docker container: olivetin-test
• Exposed API on: http://localhost:1337
• Default configuration (no authentication enabled)

Reproduction Steps

Run the following script to send 50 concurrent requests:

for i in $(seq 1 50); do
  curl -s -X POST http://localhost:1337/api/olivetin.api.v1.OliveTinApiService/PasswordHash \
    -H "Content-Type: application/json" \
    -d "{\"password\":\"flood-$i\"}" &
done
docker stats olivetin-test --no-stream
wait

┌──(root㉿kali)-[~/cve/OliveTin]
└─# docker stats olivetin-test --no-stream
CONTAINER ID   NAME            CPU %     MEM USAGE / LIMIT     MEM %     NET I/O         BLOCK I/O        PIDS
18509670bf3e   olivetin-test   344.63%   6.189GiB / 7.753GiB   79.83%    313kB / 288kB   4.31MB / 106MB   7

Docker CPU is 344.63%

This vulnerability allows unauthenticated remote attackers to:

• Exhaust server memory
• Crash the service
• Cause availability loss
• Trigger container termination in orchestrated environments

This is a Denial of Service (DoS) vulnerability affecting service availability.

Production deployments without reverse proxy rate limiting (e.g., Nginx, Traefik) are especially at risk.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2026-28342 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20260227002407-2eb5f0ba79d4); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-28342? CVE-2026-28342 is a high-severity uncontrolled resource consumption vulnerability in github.com/OliveTin/OliveTin (go), affecting versions < 0.0.0-20260227002407-2eb5f0ba79d4. It is fixed in 0.0.0-20260227002407-2eb5f0ba79d4. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. How severe is CVE-2026-28342? CVE-2026-28342 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/OliveTin/OliveTin are affected by CVE-2026-28342? github.com/OliveTin/OliveTin (go) versions < 0.0.0-20260227002407-2eb5f0ba79d4 is affected.
4. Is there a fix for CVE-2026-28342? Yes. CVE-2026-28342 is fixed in 0.0.0-20260227002407-2eb5f0ba79d4. Upgrade to this version or later.
5. Is CVE-2026-28342 exploitable, and should I be worried? Whether CVE-2026-28342 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-28342 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-28342? Upgrade github.com/OliveTin/OliveTin to 0.0.0-20260227002407-2eb5f0ba79d4 or later.