CVE-2026-57475
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 accepted unauthenticated POST requests through public-facing API endpoints that allowed a remote attacker to make limited additions to the configuration. These additions were not used by the system. 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 · moderate confidenceDeloitte AI Assist for Customer had public-facing API endpoints that accepted unauthenticated POST requests, allowing remote attackers to make limited configuration additions. These configuration modifications were not actually used by the system, limiting the impact. The vendor addressed this by restricting network access and enforcing authentication on the affected endpoints.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Identify Deloitte AI Assist for Customer deploymentSearch your asset inventory, cloud resources, or installed applications for 'Deloitte AI Assist for Customer' or 'AI Assist for Customer'. Check running services on servers for this application.Affected if The product is deployed in your environment and version is before 2026-03-25 or version cannot be confirmed.
-
Locate API endpoint URLsReview application documentation, configuration files, or network traffic logs for endpoints under paths typically associated with AI Assist (e.g., /api/, /assist/, /ai/). Check reverse proxy or load balancer configurations.Affected if You find publicly accessible API endpoints for this product.
-
Test API endpoint authenticationSend a POST request to the identified API endpoints from an unauthenticated context (no API keys, tokens, or session cookies). Use tools like curl: curl -X POST https://<endpoint> -d '{}'Affected if The endpoints accept POST requests and return successful responses without requiring authentication.
-
Verify network access restrictionsCheck firewall rules, security groups, WAF configurations, or network ACLs that control access to the API endpoints. Determine if the endpoints are exposed to the public internet (0.0.0.0/0) or restricted to authorized IP ranges.Affected if The API endpoints are reachable from the public internet without IP-based restrictions.
You are affected if Deloitte AI Assist for Customer is deployed and its API endpoints are accessible from the internet without authentication enforcement.
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 for all API endpoints. Confirm the fix addresses the original attack surface completely.
AI Assist for Customer version >= 2026-03-25
- Upgrade to AI Assist for Customer version released on or after 2026-03-25
- After upgrading, verify that authentication is now required for all API endpoints
- Confirm that network access restrictions have been applied to limit exposure of administrative interfaces
- Review access logs to ensure no unauthorized configuration changes occurred prior to the upgrade
- If running in a cloud environment, verify that network security groups or firewall rules are configured to restrict access to administrative endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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 $1,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57475 — 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-57475 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