Skip to content

Security: Reddimus/kalshi-cpp

Security

SECURITY.md

Security Policy

kalshi-cpp is a third-party C++ client for the Kalshi exchange API. It signs every request with an account-bound RSA private key, so a vulnerability that mishandles credentials or leaks request material could put live trading capital at risk. This file is the canonical contact path for reporting one.

Supported Versions

Security fixes are made on the latest published vX.Y.Z tag. Older tags are not back-patched — bump your FetchContent_Declare(... GIT_TAG ...) pin or your find_package(kalshi-cpp X.Y.Z REQUIRED) constraint to the latest minor on the same major as part of the upgrade.

Version Supported
latest tag
older

Reporting a Vulnerability

Do not open a public issue. Use GitHub's private vulnerability reporting flow, which delivers the report to the maintainer privately and tracks coordinated disclosure.

When reporting, please include:

  • Affected version (tag or commit SHA)
  • A reproduction — minimal code or test case
  • Impact (credential leak / request forgery / DoS / something else)
  • Whether you've notified anyone else (e.g. Kalshi directly)

You can expect:

  • Acknowledgement within 3 business days
  • An initial assessment + severity rating within 7 business days
  • A fix on a new vX.Y.Z+1 tag, or a clear timeline if the fix is larger

Out of Scope

  • Bugs against kalshi.com itself — those go to Kalshi's own vulnerability program, not this client library.
  • Operational issues (rate-limit handling, network blips) — file a regular issue.
  • Theoretical issues against dependencies — report them upstream (openssl, libcurl, cpp-httplib, libwebsockets, nlohmann/json, googletest). We pin via FetchContent and bump on credible advisories.

There aren't any published security advisories