Independent security researcher Eaton Zveare reported two vulnerabilities in separate CreditNirvana systems, with access to about 315,000 call recordings and 6.6 million account records. His technical investigation says both flaws were fixed on June 2, 2026.

How the two vulnerabilities differed

The call-center flaw involved a hardcoded API key in client-side JavaScript, Zveare reported. The key gave access to the call-center system, including recordings, transcripts, post-call recommendations, AI agents and campaign functions.

A separate flaw affected CreditNirvana’s main collections platform. Zveare said its authentication flow relied on a username in a request rather than validating the Keycloak token. He also reported that this vulnerability exposed administrative access to SlashRTC, a contact-center service.

The call center and the collections platform had separate reported weaknesses, so their exposed records and functions belong to different parts of the system.

Which customer records were involved?

Zveare reported about 315,000 recordings in the call-center instance for Aditya Birla Capital Finance. Separately, he reported 6.6 million accounts across customer instances for Aditya Birla Capital Finance, BharatPe and International Asset Reconstruction Company (IARC). The figures count different things: recordings in one call-center instance and accounts across three customers.

The account breakdown in his investigation assigns more than 3.4 million to Aditya Birla Capital Finance and 3.2 million combined to BharatPe and IARC. It does not give a separate figure for either of those two companies.

The reported records and functions included identity cards, credit reports, legal and settlement documents, payment receipts, emails, text messages, call logs, transcripts and collection-agent location tracking. The call-center system also exposed post-call summaries and recommendations.

When were the flaws reported and fixed?

Zveare’s chronology says he reported the vulnerabilities to India’s Computer Emergency Response Team (CERT-In) on May 30, 2026. It places the request for a proof-of-concept video, the fixes and the later vulnerability note and CVE entries on these dates:

DateEvent in Zveare’s chronology
May 30, 2026Zveare reported the vulnerabilities to CERT-In.
June 1, 2026CERT-In requested a proof-of-concept video.
June 2, 2026CERT-In confirmed it would act; CreditNirvana’s two flaws were fixed later that day.
October 26, 2026The vulnerability note and CVE-2026-110474 and CVE-2026-110475 were issued.