Skip to content

Security: SamuelSupe/graphdb

Security

SECURITY.md

Security Policy

Supported Versions

Version Security fixes
2.x Yes; use the latest 2.x release
1.x / local prereleases Superseded by 2.x; no migration support
Older No

See the latest stable release and its release validation record. Security fixes are delivered in the current 2.x release line; separate patch backports to each older minor version are not promised. Current version and data compatibility are documented in version boundaries.

Reporting A Vulnerability

Do not open a public issue containing an exploit, credential, tenant data, or unpatched vulnerability detail. Use the repository host's private security advisory channel or contact the project maintainers through the private engineering support channel. Include:

  • affected version and build commit from graphdb version;
  • deployment mode and storage/coordinator type;
  • minimal reproduction and impact;
  • whether the data/admin listeners were reachable without the gateway;
  • proposed disclosure timing, if applicable.

Maintainers should acknowledge a report, assign severity and owner, reproduce it in an isolated environment, and coordinate a fixed release before public disclosure.

Deployment Boundary

Business APIs rely on gateway authentication and authorization. X-Tenant-ID is routing metadata, not identity. Private Raft, catalog and router administration validate their shared Bearer token; this does not provide per-user tenant authorization. Production deployments must use the controls in docs/security-deployment.md, including TLS, authentication, tenant-header replacement, RBAC, listener isolation, and credential scoping.

Never attach object-store data, access tokens, or customer graph exports to a public report.

There aren't any published security advisories