GRI-2178: accept RUSTSEC-2026-0543 (chrono unmaintained) #308
No reviewers
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage!308
Loading…
Reference in a new issue
No description provided.
Delete branch "security/GRI-2178-chrono-unmaintained-advisory"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Forge issue #305,
board GRI-2178.
Security judgement
RUSTSEC-2026-0543(chrono is unmaintained), issued 2026-11-17, is INFOcategory with no CVE and no exploit — verified directly against the
advisory text.
cargo-deny's own advisory data lists no patched version;the advisory's own recommendation is a crate replacement (
jiffortime),not a version bump. That is "no safe upgrade is available" in the literal
sense
cargo deny's own error reports, not a convenience judgement.Under the product owner's rule on unmaintained advisories
(
plan/decisions/0013-advisories-block-the-merge.md, GRI-2051): "unmaintainedis ignored only with no other option... fixed is preferred over ignored, but
one or the other is required." No fix exists today, so the accept path is
the only option that unblocks
devand every open PR without a real cratemigration done under time pressure.
Residual risk, stated so it isn't lost in the config diff:
chronositson the auth path, not just display —
crates/server/src/auth/handlers.rscomputes session
expires_atwith it. There is no known defect today, butan unmaintained crate gets no fix if one is found later. That is the reason
this is dated and tracked, not a bare ignore.
Removal condition: forge issue
#307,
closed by a
chrono->jiff/timemigration acrossclient/server/shared(and whatever drops the transitive pull through
sqlx-core).-D advisory-not-detectedalready re-reds the gate the day either that migrationlands or a maintained chrono fork clears the advisory, so the entry cannot go
stale unnoticed.
Verified independently, not just from the reporter's evidence
cargo deny advisoriesfailing on PR #303 @c8230e3, CI run 570job 6,
failureat 12:30:15Z today — matches the reported timeline.CVE, no patched version, reference is a GitHub maintenance-status issue.
cargo deny check advisories -D advisory-not-detectedpasses clean on thisbranch.
./scripts/local-gates.sh --rust-onlypasses clean (fmt, clippy, deny,bans, licenses, sources, cargo test) — exit 0.
Test plan
cargo deny check advisories -D advisory-not-detected— passesscripts/local-gates.sh --rust-only— every gate passescargo deny advisories, green