Security

Vulnerability disclosure policy

Found a vulnerability in CodeB software, on one of our websites or in the CodeB Wallet? Tell us. This page says how to report it, what happens next, and which timelines we commit to.

ENDE

How to report

Email
info@aloaha.com · subject “Security”
Languages
English, German
Machine-readable
/.well-known/security.txt (RFC 9116)

Please include: the affected product and version or the address of the page, the steps to reproduce, the possible impact, and how we can reach you. Do not send real personal data of other people or any credentials; a proof with test data is enough. For confidential details we arrange an encrypted channel on request.

What happens next

Acknowledgement
within two business days, by a person
Assessment
we rate the report (critical, high, medium, low) and tell you the result
Fix
we keep you informed about progress and tell you when the fix is available
Disclosure
coordinated with you; 90 days from the report by default, shorter when the issue is actively exploited
Credit
on request we name you in the release notes

We do not run a paid bug-bounty programme.

Our reporting timelines

Critical or actively exploited
within 24 hours of becoming aware: early warning to the competent authority (CSIRT / ENISA) and notice to the affected operators
High
within 72 hours: notice to the affected operators with our assessment and the available mitigations; for actively exploited vulnerabilities and severe incidents, the full notification to the competent authority
Medium and low
with the next release, documented in the release notes

The timelines for actively exploited vulnerabilities and severe security incidents follow Regulation (EU) 2024/2847 (Cyber Resilience Act). More on the cyber resilience page.

Scope

In scope: the CodeB Sovereign Communications server software (meetings, telephony, Voice AI, OIDC identity provider, wallet verifier and issuer), Credential Provider V2, the websites and services operated by Aloaha Limited, and the CodeB Wallet for Android.

Customer deployments: CodeB is self-hosted. If your report concerns the set-up of a particular operator, please use that operator’s security.txt. If the cause is in our software, report it to us as well.

Out of scope: third-party services, social engineering, physical access, load or denial-of-service testing, and findings without a security impact.

Good-faith research

If you act in good faith and follow this page, we will not take legal action against you. That means: use only your own accounts and test data, do not access or change other people’s data, do not disrupt the service, do not exploit the issue further than needed to show it, and give us time to fix it before you publish details.

Every report is read and answered by a member of the engineering team. No auto-responder, no ticket queue.

Last updated: 12 November 2026 · © 2026 Aloaha Limited