v3.10.5

Released October 22, 2026

Improves accessibility and white-label theming, fixes access to the API Keys screen, and hardens the document parser against distrusted certificate authorities.

Confirming this release. Users who are allowed to create API keys now see the API Keys screen even where role‑based capabilities aren’t enforced, and buttons and links meet AA color contrast. These changes are largely behind‑the‑scenes — confirm your deployment’s version with your Ask Sage administrator.

🔧 Improvements & fixes

• The API Keys screen now appears for everyone allowed to create keys. On deployments that don’t enforce role‑based capabilities, some users could create API keys but the API Keys screen was hidden from them. The screen now appears for any user who is permitted to create keys.
• More readable buttons, links, and controls (accessibility). Color contrast has been improved so labels and controls meet accessibility standards (WCAG AA / Section 508) — for example, the text on red delete/error buttons in dark mode is now clearly readable.
• White‑label branding now supports light and dark mode. White‑label deployments can set distinct brand and accent colors for light mode and dark mode, so custom branding stays readable in both.

🛡️ Security & vulnerability remediation

• Removed distrusted certificate authorities from the document parser. The document parser is rebuilt with an updated trust bundle that drops certificate authorities revoked under a recent advisory (CVE‑2026‑111943), as part of Ask Sage’s continuous‑monitoring commitment.

🔒 Security & platform

Ask Sage services are delivered as FIPS‑hardened, digest‑pinned, and cosign‑signed images within the FedRAMP Class D authorization boundary, and are continuously rebuilt against the latest patched base images as part of Ask Sage’s continuous‑monitoring commitment.