Critical
CVSS 9.1 API Key Exposure Responsible Disclosure
Disclosure
Production API Authentication Bypass via Encryption Key Exposure
Finding 2: Production API Authentication Bypass via Encryption Key Exposure The API gateway validation uses an AES-256-CBC encrypted `X-Request-ID` header. The encryption key, IV, API key, and subscription key are all exposed in client-side JavaScript, allowing anyone to forge va
- Target
- African Remittance Provider
- Category
- API Key Exposure
- Channel
- Responsible Disclosure
- Disclosed
- 2026-04
Redaction note
Vendor identity withheld.
This finding is documented here as part of MemCyber’s public disclosure record. The vendor has been anonymized to a sector and region descriptor. Full technical detail — including root cause, reproducible proof-of-concept, remediation guidance, and vendor attribution where granted — is available to qualified prospects under NDA.
Coordinated disclosure
How we handled it.
- Reported to the vendor via Responsible Disclosure with a reproducible proof-of-concept.
- Triage + remediation window coordinated with the vendor security team.
- Fix verified before any public reference.
- This record published only after the embargo period closed.