Live › vulnerability › CVE-2026-107840
Go to dashboardyopass, a service for sharing secrets, lets any unauthenticated client send requests with arbitrary HTTP method names, and its metrics middleware stores each one as a new Prometheus label. An attacker can flood the server with unique methods so memory grows until the process is OOM-killed, and /metrics slows or stops being useful.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/jhaals/yopass | go | < 0.0.0-20260727191436-61e31ead04a4 | 0.0.0-20260727191436-61e31ead04a4 |
14.7.0) is affected14.7.0)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
yopass is a service for securely sharing secrets, passwords, and files. Prior to version 14.7.0, the Prometheus metrics middleware in pkg/server/server.go uses the attacker-controlled r.Method value directly as the method label for yopass_http_requests_total and yopass_http_request_duration_seconds. Because the catch-all route accepts arbitrary HTTP method tokens, an unauthenticated remote attacker can submit many unique methods and create metric series that the Prometheus registry never evicts. The resulting monotonic memory growth can OOM-kill the process, while the expanding registry also degrades /metrics scrape latency and can blind monitoring. This issue is fixed in version 14.7.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-107840")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.