Advisories
For your digest

github.com/openbao/openbao: OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack

It touches something Phylax follows. No evidence of use yet.

Does it affect what I run?

github.com/openbao/openbao (Go)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • github.com/openbao/openbao (Go): every version, before 0.0.0-20260713141742-763625a20721
  • github.com/openbao/openbao (Go): from 0.1.0, up to and including 1.1.5
  • github.com/openbao/openbao (Go): every version, before 0.0.0-20260713141742-763625a20721; from 0.1.0, with no fixed release listed

The fix

  • github.com/openbao/openbao (Go) fixed in 0.0.0-20260713141742-763625a20721

    go
    go get github.com/openbao/openbao@v0.0.0-20260713141742-763625a20721
    Check what is installed
    go list -m github.com/openbao/openbao
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Go dependency github.com/openbao/openbao to 0.0.0-20260713141742-763625a20721 or the nearest later release, to fix CVE-2026-63132. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

No evidence that it is being used, or can be. It is listed because of what it affects.

Timeline

  1. First published here, as "For your digest".