EUVD-2026-109786
GHSA-72fh-w73q-9x49
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDownload client-side JavaScript bundle
-
ExploitExtract hardcoded static API key
-
ExecutionAuthenticate to application API with key
-
ImpactRetrieve call transcripts and recordings
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
|
| Exploitation Conditions | No special conditions - remote unauthenticated exploitation against default deployments of the CreditNirvana Agentic AI Call Centre, because the static API key is shipped inside the publicly downloadable client-side JavaScript bundle and requires no authentication (PR:N) or user interaction (UI:N) to extract. The only practical limiting factors are that the target application instance must be internet-reachable and that the extracted key grants access only to the data exposed through the application API (call transcripts and recordings); no integrity or availability impact applies (VI:N/VA:N). |
| Impact | The CVSS 4.0 signals point to a genuinely easy-to-trigger confidentiality flaw: AV:N/AC:L/AT:N/PR:N/UI:N means remote, unauthenticated exploitation with no special conditions, while VC:H/VI:N/VA:N confirms the impact is read-only data exposure (call transcripts and recordings) with no integrity or availability effect. The base score of 8.7 is driven almost entirely by the trivial exploitability of a hardcoded key (CWE-321) rather than by broad impact. No EPSS score, KEV listing, or POC reference was supplied, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the vuln.today Decision label of 'this_week' and the CERT-In advisory indicate a near-term patch priority rather than an emergency. The practical risk is bounded by the product's apparent niche footprint: a flaw this easy to exploit would be high priority wherever the product is deployed, but the obscure single-vendor product likely limits the exposed population. Note the input Tags label this 'RCE', which conflicts with the CVSS impact metrics (VI:N/VA:N and CWE-321) - the actual impact is sensitive-data disclosure, not code execution; treat the RCE tag as erroneous. |
| Exploit ScenarioDerived | An unauthenticated attacker visits the CreditNirvana Agentic AI Call Centre web application, downloads its client-side JavaScript bundle, and extracts the hardcoded static API key embedded in that code. Using the key, the attacker issues arbitrary calls to the application's API and retrieves stored call transcripts and recordings. No public exploit code has been identified, but the technique requires only a browser and standard HTTP tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
CreditNirvana's Agentic AI Call Centre ships a hardcoded static API key inside its client-side JavaScript bundle, so anyone who can reach the application can download the bundle, extract the key and use it to call the application API. The result is remote, unauthenticated read-only exposure of call transcripts and recordings (CWE-321); integrity and availability are unaffected. The reporting source is CERT-In and the priority signal places it in the 'this week' handling window; no public exploit code or confirmed active exploitation was identified at time of analysis.
RemediationAI
No vendor-released patch or fixed version is identified in the available data; the CERT-In note CIVN-2026-0523 (https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES01&VLCODE=CIVN-2026-0523) is the reference to track for an official update. Until then, the highest-value action is to rotate the exposed static API key immediately and invalidate the old value, accepting the brief disruption of any legitimate client still using it. Next, remove the credential from the client-side JavaScript bundle and move API access behind server-side token exchange or short-lived, per-session scoped tokens, which requires development effort but eliminates the class of issue. As compensating controls, require authenticated sessions for the transcript and recording endpoints rather than accepting a bare static key, restrict the API to known source IP ranges or a VPN (trade-off: breaks mobile and remote-agent access), and apply rate limiting plus alerting on bulk transcript or recording retrieval to catch abuse of a leaked key. Because the exposure is read-only and historical recordings cannot be un-leaked, also review API access logs for anomalous enumeration of call transcripts and recordings and treat any such data as potentially disclosed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-321, Use of Hard-coded Cryptographic Key: a static API credential is embedded in JavaScript that is served to every browser that loads the application, which makes the secret effectively public because any visitor can retrieve it with developer tools or a simple HTTP request. Because the key is a long-lived static value rather than a per-session token, possession of it substitutes for authentication against the application API, and the assessed CVSS:3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N reflects precisely that: no privileges (PR:N), no user interaction (UI:N) and no attack complexity beyond fetching a file, with a high confidentiality-only impact. The CPE entry cpe:2.3:a:creditnirvana:agentic_ai_call_centre:*:*:*:*:*:*:*:* is unversioned, meaning the source data does not bound the affected version range, and the only reference is the CERT-In vulnerability note CIVN-2026-0523, which should be treated as the authoritative version scope. One feed tag mentions RCE, but that does not match the assessed vector or the description, both of which describe read access to transcripts and recordings only; no code execution path is described in the available sources, and the trigger conditions beyond 'download and inspect the JS bundle' are not described in detail.
Know when Agentic Ai Call Centre gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Key is extractable from public client-side JS with no auth or interaction (AV:N/AC:L/PR:N/UI:N); impact is confidentiality-only data exposure (C:H, I:N, A:N), scope unchanged.
Primary rating from Vendor (CERT-In).
CVSS VectorVendor: CERT-In
DescriptionCVE.org
This vulnerability exists in the CreditNirvana Agentic AI Call Centre application due to hardcoded static API Key in the client side JavaScript bundle. An unauthenticated remote attacker could exploit this vulnerability by downloading client side JavaScript files and extracting API key, which could lead to make arbitrary API calls to retrieve call transcripts and recordings through the application API of the targeted system.
Executive ViewAI
CreditNirvana's Agentic AI Call Centre contains a hardcoded API key in its client-side JavaScript, enabling unauthenticated read-only access to sensitive call transcripts and recordings. This affects customer privacy and regulatory compliance, requiring immediate leadership attention due to potential data exposure and reputational harm.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting network access to the application, monitoring API usage for unauthorized access, and rotating the exposed API key if feasible.
Threat Intelligence Overview
NVD
CVE.org
EPSS
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
Exploit-DB