Skip to content
The Docs Report
Tuesday, November 17, 2026NewsletterRSS

Speakeasy CLIs Now Refuse Redirects That Would Leak Credentials

Speakeasy 1.804.0 and 1.805.0 stop generated CLIs from following cross-origin redirects and mask credentials in errors, debug logs and body previews.

2 min read

SpeakeasyCLISecurity

Isometric 3D illustration of glossy cobalt blue brass keys on a tiled floor

Command-line tools that Speakeasy generates now refuse cross-origin redirects, according to the Speakeasy changelog entry for version 1.804.0, dated Oct. 27. Credentials go only to the configured server. Version 1.805.0, dated Oct. 28, masks credentials in error output and debug logs.

Redirects can no longer carry credentials elsewhere

Speakeasy’s 1.804.0 entry says the CLI “refuses cross-origin redirects so credentials are only sent to the configured server.” The change is listed under bug fixes.

The same release lets declarative command flags imply other request body values. Speakeasy’s example is a background flag that turns streaming off.

Credentials are masked in output

Speakeasy said version 1.805.0 masks resolved credentials from flags, environment variables, the OS keychain or config in rendered error output and --debug logs. A server that echoes a credential back no longer makes it print.

Header-named fields such as Authorization are also masked inside request and response body previews, with the structure kept. Errors no longer echo the raw input when a request body or JSON flag value fails to decode into a union type.

Smaller CLI fixes in the same releases

--dry-run now writes its JSON preview to stdout in every machine output mode, including agent mode, YAML and toon. --all keeps fields the spec doesn’t declare when it prints pages as JSON or through --jq. whoami shows the effective output format and where it comes from.

Version 1.803.2, dated Oct. 23, made generated Go modules require Go 1.26.10. That toolchain rejects the compromised eMudhra emSign certificates the changelog names.

Python SDKs change too

Python v2 SDKs stop sending empty-string credentials as an empty bearer token, API key header or query parameter. Version 1.805.0 adds a modelSerializationMethods option for to_dict and to_json model helpers. Unrecognized open enum values now come back from to_dict as plain str and int.

Key takeaways

  • Generated CLIs refuse cross-origin redirects as of Oct. 27.
  • Credentials from flags, environment variables, the keychain and config are masked in errors and --debug logs as of Oct. 28.
  • Fields named like Authorization are masked in body previews.
  • Python v2 SDKs no longer send empty credentials.

The take

We think the redirect rule is the more important of the two changes. A credential is meant for one server. A redirect that carries it to a second server turns the first server’s mistake into a leak. Refusing the hop keeps the credential where you sent it. Masking in logs matters for a different reason: debug output gets pasted into tickets and chat. Teams that ship a generated CLI should regenerate it. Then run a failing command with --debug and read the output for anything secret. Report any leak to Speakeasy.