CVE-2026-57474
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDeloitte AI Assist for Customer disclosed some configuration information through public-facing API endpoints that accepted unauthenticated requests. This information could reduce an attacker’s reconnaissance effort. On 2026-03-25, AI Assist for Customer restricted network access and enforced authentication for the previously exposed endpoints.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDeloitte AI Assist for Customer had API endpoints that accepted unauthenticated requests and exposed configuration information to public-facing networks, potentially aiding attackers in reconnaissance.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026-03-25CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed versionLocate the version information for Deloitte AI Assist for Customer (check application metadata, about page, or version file) and compare it to the affected version threshold of 2026-03-25Affected if The installed version is dated before 2026-03-25
-
Identify API endpoint exposureReview network configuration and firewall rules to determine if the Deloitte AI Assist for Customer API endpoints are reachable from public-facing networksAffected if API endpoints are exposed to untrusted networks without network-level access restrictions
-
Test API authenticationAttempt to access the API endpoints (typically found at /api/ or similar paths) without providing any credentials or authentication tokensAffected if The API endpoints respond successfully to unauthenticated requests
-
Check for configuration exposureSend requests to the API and inspect the responses for sensitive configuration information such as internal URLs, credentials, connection strings, or system detailsAffected if The API returns configuration or system information to unauthenticated callers
You are affected if your installed version predates 2026-03-25 AND your API endpoints are accessible from public networks without authentication, allowing attackers to retrieve configuration details.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026-03-25
Verify that network access restrictions and authentication enforcement are properly configured and functioning as intended on the affected endpoints.
2026-03-25 or later release of Deloitte AI Assist for Customer
- 1. Identify the current installed version of Deloitte AI Assist for Customer
- 2. If running a version prior to 2026-03-25, obtain and install the 2026-03-25 release or later from Deloitte
- 3. Verify that network access controls are configured to restrict exposure of API endpoints to untrusted networks
- 4. Confirm that authentication is now required for all API endpoints that were previously unauthenticated
- 5. Validate the fix by attempting unauthenticated access to previously exposed API endpoints - requests should be denied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57474 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57474 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data