# Security Policy

## Supported Versions

Currently only the following versions of Kuberna Labs are being supported with security updates.

| Version | Supported          |
| ------- | ------------------ |
| 1.0.x   | :white_check_mark: |
| < 1.0   | :x:                |

## Reporting a Vulnerability

Security is a top priority for Kuberna Labs, especially given our focus on autonomous agents managing cross-chain funds and TEE deployments.

If you discover a security vulnerability in this project, **please do not report it by creating a GitHub issue**. Instead, follow these steps:

1. Send an email to [security@kubernalabs.com](mailto:security@kubernalabs.com).
2. Include a detailed description of the vulnerability, the conditions under which it occurs, and any potential impact.
3. If possible, provide a proof-of-concept (PoC) or steps to reproduce the issue.

### Response Timeline

We take all security reports seriously and commit to the following response timeline:

- **Acknowledgment**: Within 24 hours of receiving your report.
- **Initial Assessment**: Within 48 hours, we will confirm the vulnerability and provide an estimated timeline for a fix.
- **Resolution**: We aim to resolve critical vulnerabilities within 72 hours.
- **Disclosure**: Once a fix is deployed and verified, we will coordinate public disclosure, giving appropriate credit to the reporter.

### Bug Bounty

At this time, we do not have an official bug bounty program, but we review high-impact reports on a case-by-case basis and may offer rewards for critical findings related to our smart contracts or core intent protocol.

Thank you for helping keep Kuberna Labs secure!
