Disclosed weakness · no CVE recorded
LiteLLM budget boundaries could renew allowances too early
LiteLLM · LiteLLM Proxy · budget window scheduling
First documented disclosure · Review checkpoint
Summary
Timezone handling, elapsed-period rounding and repeated daylight-saving times could clear spending counters before the configured period ended.
Severity and exploitation evidence
No CVSS score recorded in this review.
Exploitation not established: Reviewed maintainer reports and controlled checks do not establish malicious exploitation against users.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
Window due checks discarded timezone offsets; reset calculations lost multi-day offsets or re-aligned saved elapsed schedules, and calendar boundaries could repeat during a clock change.
Conditions required
An operator relies on affected budget windows: non-UTC offsets, multi-day elapsed durations, non-divisor durations such as 45m, or repeated local calendar reset times.
Potential impact
Spending allowances can reopen early or repeatedly, permitting more usage than the intended period limit. Positive timezone offsets can also delay resets.
Affected versions and configurations
Maintainer-controlled pre-fix snapshots are affected; a complete earlier release range is not established.
Fix and mitigation status
Prerelease 1.112.0-dev.2 lists PR53012, PR53020, PR53151 and PR53065. Reviewed tagged code retains UTC due checks and elapsed/calendar corrections; no stable release containing this combined correction was verified.
Practical next steps
Use a verified corrected build and inspect actual reset instants and retained spend across consecutive windows and daylight-saving changes. Review previously stored schedules separately.
Operating lesson
Store and compare authoritative budget boundaries consistently, including timezone and elapsed-period semantics.
Evidence and limits
This groups related boundary-accounting corrections disclosed November 20, distinct from the existing long-unit-spelling mismatch. Upstream reports controlled proxy and database checks; this review inspected source without executing them. Initial aligned windows can still be shorter than the nominal duration; unanchored multi-day app windows retain daily re-alignment. Legacy inline windows acquire calendar starts on rollover, and the multi-day offset fix does not rewrite already stored reset timestamps. No malicious exploitation or CVSS score was established.
Sources
- UTC budget-window due-check correction
Primary source ·
- Multi-day offset correction
Primary source ·
- Elapsed schedule preservation
Primary source ·
- Calendar and daylight-saving correction
Primary source ·
- LiteLLM development release 1.112.0-dev.2
Primary source ·
- Development tag duration boundary implementation
Primary source ·
- Development tag budget-window due checks
Primary source ·