GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Build software better, together

Security: crate/crate

Security

Report a vulnerability

SECURITY.md

Security Issues

The CrateDB team and community take security bugs seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.

Reporting Security Issues

To report a security issue, please use the GitHub security reporting system on the corresponding project where you discovered the flaw. It is on the "Security" tab at Security » Advisories » New draft security advisory.

For CrateDB, just navigate to Report a vulnerability for CrateDB.

Please do not report denial of service issues for authenticated users as security issues, use the public issue tracker instead for those. In a database system it is generally possible for a single user to create a lot of load with little effort, therefore we don't consider Denial of Service issues critical except if they're possible for unauthenticated users.

The CrateDB team will send a response indicating the next steps in handling your report. After the initial reply to your report, the security team will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.

Alternative Communication

If you can't use the GitHub security reporting system, an alternative way of reporting security issues will be to write an email to [email protected].

  • Authorization bypass: scalar subqueries inside VALUES/table-function arguments are not privilege-checked, allowing unauthorized table reads
    GHSA-2xvq-gg9f-54p9 published Nov 9, 2026 by matriv
    Moderate
  • Unauthenticated concurrent gzip request bodies can terminate CrateDB with heap exhaustion
    GHSA-qcp3-r37v-7p8j published Nov 9, 2026 by matriv
    High
  • Any authenticated PostgreSQL client can switch to CrateDB's unauthenticated internal transport protocol and bypass role-based access control
    GHSA-ppqq-957g-9jpc published Nov 9, 2026 by matriv
    High
  • Dropped PostgreSQL users can execute retained prepared portals
    GHSA-jp7h-6782-g32q published Nov 9, 2026 by matriv
    High
  • Long-lived PostgreSQL sessions retain revoked table privileges
    GHSA-7p46-fxpg-cwm7 published Nov 9, 2026 by matriv
    High
  • CrateDB certificate-authenticated non-superusers are given a superuser session on the HTTP API
    GHSA-49gw-4r68-7f6c published Oct 12, 2026 by matriv
    High
  • Uncapped PostgreSQL MSG frame length + no read timeout enables unauthenticated memory-accumulation DoS
    GHSA-gvhg-w5hf-g282 published Sep 8, 2026 by matriv
    High
  • RESTORE SNAPSHOT overwrites live role/privilege metadata with only DDL on CLUSTER — privilege escalation
    GHSA-q2wh-fx2h-rqfh published Sep 8, 2026 by matriv
    High
  • Missing DQL authorization on UPDATE/DELETE subqueries allows reading arbitrary tables with only DML
    GHSA-cf3f-xgm5-jfrm published Sep 8, 2026 by matriv
    Moderate
  • HTTP auth handler caches authorized user per connection and skips credential re-validation -> auth bypass behind a connection-pooling proxy (conditional)
    GHSA-8jr8-9wjf-7m2h published Sep 9, 2026 by matriv
    Moderate
Learn more about advisories related to crate/crate in the GitHub Advisory Database
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.