Security researcher Eaton published a full compromise walkthrough of Credit Nirvana's agentic debt-collection stack on November 18, 2026, assigning CVE-2026-110474 and CVE-2026-110475. The write-up shows how authentication could be skipped, Keycloak session handling could be bypassed in the browser, and backend APIs trusted the wrong headers, exposing agentic call tools and enterprise collections data tied to Aditya Birla Capital Finance.
This is not a theoretical agent prompt attack. It is production fintech software marketing AI agents for collections, with hundreds of thousands of call recordings reachable when identity checks fail.
TL;DR: what Eaton demonstrated #
| Surface | What Eaton reported |
|---|---|
| Agentic call center | Call Transcriber , disposition, post-call recommendations, call audit agents |
| Recordings | ~315,000 stored calls with playback |
| Core platform | CollectionWorkz Credit Nirvana instance forAditya Birla Capital Finance |
| Auth flaws | Hardcoded API key , unused Cognito token,10k+ users via unauthenticated list API |
| IAM | Keycloak client patches with fake JWTs; server trusteduserName in body over token |
| CVEs | CVE-2026-110474 ,CVE-2026-110475 |
Why agentic collections are a high-value target #
Debt-collection software already holds names, account numbers, payment history, and call audio. Vendors now brand the same stack as agentic AI: real-time transcription, sentiment analysis, next-best-action recommendations, and proactive outreach campaigns before accounts go delinquent.
Eaton's screenshots and descriptions show those features as first-class modules, not future roadmap slides. An attacker who gains operator-grade access can replay calls, study negotiation tactics, and map which agents run automatically — intelligence useful for fraud, social engineering, and regulatory embarrassment.
The incident belongs in the same conversation as GAO tests showing models draft attack plans and agent breach trackers, but the exploit chain here is Web 101: missing server-side authorization on APIs behind a React single-page app.
Agent code review pair illustrating weak auth around Credit Nirvana agentic debt tools
Attack chain: from hardcoded key to full control #
Enterprise pilot rollout metaphor for agentic collections UIs that skip server-side auth checks
Eaton's narrative starts at the agentic call center, where a hardcoded API key made the Amazon Cognito login unnecessary. The returned Cognito token was never validated server-side, so skipping login was enough to reach privileged features.
On the main CollectionWorkz deployment, Eaton traced React bundles, found a users-list API returning more than 10,000 accounts without authentication, and pivoted to Keycloak integration. By feeding syntactically valid but invalid JWTs and patching client-side refresh logic, the browser could be convinced a session might exist.
The critical backend mistake: Credit Nirvana's login API honored userName in the JSON body while sending a Keycloak token in Authorization-Token that was not verified. Eaton picked a high-privilege username from the leaked list, obtained a cnToken GUID, and discovered that subsequent requests worked when fake Keycloak headers were stripped and only CN-Token remained.
That pattern — trusting an application token while ignoring the enterprise IAM token — is how agent orchestrators and human portals get owned in the same request path.
What data classes were exposed #
Eaton describes call recordings with transcripts, disposition analytics, campaign builders for AI-powered outreach, and an AI Agent Registry to browse agents inside the collection system. On the core platform, user tables, role metadata, and collections workflows across secured and unsecured products were in scope once APIs accepted the CN-Token.
Eaton notes Aditya Birla Capital Finance customers as impacted on the Agentic AI Call Center, and documents a far larger CollectionWorkz exposure on the primary platform: 6.6 million accounts across Aditya Birla Capital Finance, BharatPe, and International Asset Reconstruction Company (IARC), with ID cards, credit reports, legal documents, and call recordings in scope. Credit Nirvana and Perfios fixed both issues in June 2026 after CERT-In coordinated disclosure; the November 18 article is Eaton's public write-up, not a final statutory breach notice. Check issuer advisories and Indian regulatory filings for confirmed customer-notification timelines.
What developers building agents should fix #
- Never embed long-lived API keys in front-end JavaScript. Any key shipped to browsers is public.
- Validate IAM tokens on the server for every route (Keycloak'stoken validation docs describe local JWT checks and introspection), including internal microservices behind your agent UI.
- Do not accept usernames from request bodies when a bearer token is present. Bind identity toverified claims only.
- Treat agent registries like admin consoles. They revealtool names, prompts, and automation scope attackers need for follow-on abuse.
- Log and alert on unauthenticated list endpoints such as**
/users-list** patterns Eaton highlights.
Teams shipping MCP-connected agents should compare this to MCP tool provider misbinding and Microsoft's PyPI credential stealer targeting agent frameworks — different entry points, same lesson: agents amplify impact when auth is weak.
How to protect collections and agent platforms #
If you operate voice agents, collections SaaS, or internal agent hubs:
- Run external pen tests that assumebrowser tampering , not onlyOWASP Top 10 scanners .
- Segment call storage withper-tenant encryption andbreak-glass access logging .
- Apply rate limits andanomaly detection ontranscript download APIs .
- Require step-up authentication beforecampaign launch oragent registry edits .
For runtime guardrails on autonomous tools — approving transfers, sending messages, or changing account state — teams can use platforms such as AgentBeam to block dangerous agent actions before they execute, alongside fixing the authorization bugs Eaton documented.
Collections agents versus coding agents: different blast radius #
Many teams worry about Claude Code prompt injection or Codex sandbox escapes. Collections agents add telephony and regulated speech:
- Outbound dialers can harass consumers if misconfigured.
- Transcripts may includethird-party bystanders on speakerphone.
- Disposition models influencelegal escalation paths.
Eaton's post is a reminder that the scariest agent failures may be missing auth on /users-list, not clever jailbreaks. When you prioritize controls, inventory admin routes before you tune system prompts.
Keycloak and React SPAs: why client patches are not security #
Eaton documented disabling refresh handlers and short-circuiting userinfo calls inside the browser. That is powerful for proof of concept, and terrifying for defenders, because it shows how little the server cared.
Production fixes must assume attackers control the client:
| Bad pattern | Safer pattern |
|---|---|
Trust userName in JSON body |
Bind identity to validated JWT claims server-side |
| Accept requests with only app token | Require IAM token + app token with matching subject |
| Ship API keys in bundles | Use short-lived tokens from backend exchange |
| Expose user enumeration APIs | Gate lists behind admin RBAC andrate limits |
Credit Nirvana's CN-Token header behaving like a session cookie without binding to Keycloak matches failures seen in MCP tool misbinding where routers treat metadata as proof of identity.
Disclosure timeline and what to watch next #
Eaton published on November 18, 2026 with CVE-2026-110474 and CVE-2026-110475 identifiers in the title and metadata. The author notes another Keycloak-related issue planned for December, suggesting coordinated disclosure cadence.
Customers should monitor:
- Credit Nirvana orAditya Birla Capital Finance security statements
- CERT-In or sector regulators if notifications become public
- CISA KEV listing if vendors assignCVSS andactive exploitation proof
Until then, treat Eaton's article as technical primary source, not a final victim count.
Red-team checklist for agentic fintech UIs #
Use this as an internal test plan:
- Download the production JavaScript bundle and grep for
apiKey,cognito, andBearer. - Call every
/usersand/agentslist route without cookies. - Replay tokens from a low-privilege user againsthigh-privilege routes .
- Remove headers one at a time to see which the APIactually enforces .
- Attempt campaign creation withoutMFA if the product claimshuman approval .
These steps mirror how nginx2root HTTP/2 RCE and Java4Shell reached production — boring HTTP, enormous impact.
Regulatory and industry context #
Agentic collections sit under fair debt, telemarketing, and financial privacy rules in multiple jurisdictions. A breach that exposes call audio and AI-generated dispositions can trigger contractual penalties even before class actions arrive.
The case also feeds felony-bench-style tracking of agents affecting real third parties: here the harm is data exposure, not an autonomous wire transfer, but collections agents can still initiate outbound contact when operators misuse restored access.
Related reading #
Why this belongs on the felony-bench thread #
explainx.ai tracks agents that harm third parties on felony-bench. This incident is data exposure, not an autonomous funds transfer, but it shows agent branding on high-risk workflows without agent-grade authorization.
Security teams should log it beside GitHub and Microsoft's MDASH disclosure pipeline as a case where "agentic" marketing outpaced API maturity.
Related workshops and skills #
If your team is shipping voice or text agents into regulated industries, pair technical fixes above with live agent workshops on permission models and eval harnesses before you enable outbound automation. Eaton closes by noting that Keycloak client tricks may apply to other React apps facing a December disclosure. Even if you do not run Credit Nirvana, re-test your IAM integration any time you ship new agent dashboards to customer support or collections teams.
Technical details and CVE identifiers come from Eaton's November 18, 2026 article. Impact scope for specific customers may change as vendors publish advisories.