Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-115333 Overview
CVE-2026-115333 is an improper authentication vulnerability [CWE-287] in Lotus through version 0.10.2. The flaw resides in the Go event ingestion middleware, which validates API keys by prefix only. The middleware does not compare the submitted secret against the stored hashed_key. Attackers who learn or guess an API key prefix can submit arbitrary usage events to POST /api/track/ while impersonating a target organization. This manipulation alters metered usage records and distorts downstream billing. Lotus is an open-source pricing and billing platform, so the integrity impact extends directly to revenue data.
Critical Impact
Any party with knowledge of an API key prefix can forge usage events for a victim organization, corrupting metered billing data at POST /api/track/.
Affected Products
- Lotus (uselotus/lotus) versions through 0.10.2
- Go event-ingestion service (go/event-ingestion/authn/authn.go)
- Deployments relying on the /api/track/ endpoint for metered billing
Discovery Timeline
- 2026-10-22 - CVE-2026-115333 published to the National Vulnerability Database (NVD)
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-115333
Vulnerability Analysis
Lotus issues API keys composed of a public prefix and a secret component. The secret is stored server-side as a hashed value (hashed_key) to allow constant-time comparison during authentication. In the affected Go event-ingestion middleware, the authentication routine extracts the prefix from the incoming request and looks up the matching organization record. It then treats a successful prefix lookup as proof of authentication and skips verification of the secret portion against hashed_key.
This omission reduces the authentication secret to its public identifier. Prefixes are not designed to be confidential and may appear in logs, client-side telemetry, support tickets, or screenshots. An attacker who obtains a prefix inherits the ability to submit events as the owning organization. The impact is scoped to the event ingestion path, which drives metered usage calculations and invoicing.
Root Cause
The root cause is a missing secret comparison in the authentication path at go/event-ingestion/authn/authn.go lines 85-95. The middleware resolves the API key record by prefix and returns success without invoking the hash verification step. This represents a classic broken-authentication pattern where identification is conflated with authentication.
Attack Vector
Exploitation requires network access to the Lotus event ingestion endpoint and knowledge of a valid API key prefix. The attacker crafts an HTTP POST request to /api/track/ containing arbitrary event payloads. Because the server validates only the prefix, forged events are accepted and attributed to the victim organization. Repeated submissions inflate or distort billing metrics and can be used to disrupt revenue reporting or trigger unexpected charges.
No synthetic exploit code is reproduced here. Refer to the VulnCheck Advisory for Lotus and the GitHub Lotus Authn Code Snippet for the vulnerable code path.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-115333
Indicators of Compromise
- Unexpected POST /api/track/ requests from source IPs that do not match known customer infrastructure.
- Sudden spikes or anomalies in metered usage counters that do not correlate with application activity.
- Billing reconciliation discrepancies between application-side event logs and Lotus-ingested events.
Detection Strategies
- Correlate ingested events in Lotus against first-party application telemetry to identify events that have no upstream origin.
- Log and alert on event submissions where the source IP, user agent, or geolocation deviates from the organization's historical baseline.
- Hunt for repeated POST /api/track/ calls that reuse a prefix but omit or malform the secret portion of the API key.
Monitoring Recommendations
- Enable verbose access logging on the Go event ingestion service and ship logs to a centralized data lake for retention and analysis.
- Track per-organization event submission rates and alert on statistical outliers.
- Monitor rotation events for API keys and alert when previously retired prefixes continue to receive traffic.
How to Mitigate CVE-2026-115333
Immediate Actions Required
- Restrict network exposure of the Lotus event ingestion endpoint to trusted sources until a patched release is deployed.
- Rotate all API keys so that any prefixes exposed in logs or client code become invalid.
- Audit historical events on /api/track/ for the affected period and flag organizations with anomalous usage for billing review.
Patch Information
At the time of publication, the advisory describes Lotus through 0.10.2 as affected. Review the GitHub Lotus Repository and the VulnCheck Advisory for Lotus for upstream fix status. The remediation requires the middleware to compare the submitted secret against the stored hashed_key using a constant-time hash verification before granting access.
Workarounds
- Place the event ingestion service behind an authenticating reverse proxy that enforces mutual TLS or an additional shared secret.
- Apply IP allowlisting at the ingress layer to limit /api/track/ access to known customer egress ranges.
- Deploy a short-term middleware shim that rejects requests whose API key does not pass a full hash comparison against hashed_key.
# Configuration example: restrict /api/track/ at an Nginx reverse proxy
location /api/track/ {
allow 203.0.113.0/24; # trusted customer range
deny all;
proxy_pass http://lotus-event-ingestion;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

