I Scanned 1 Million AI Services. Here's What Worries Me More Than the Vulnerabilities
A recent scan of one million AI services revealed alarming security vulnerabilities. The findings indicate widespread failures in basic security practices such as authentication and rate limiting. This highlights a concerning trend where teams apply less security rigor to AI services compared to traditional network services.
- ▪The scan found that almost no AI services implemented proper authentication on inference endpoints.
- ▪Many services lacked rate limiting, making them vulnerable to resource exhaustion attacks.
- ▪Training data was often exposed through logs, revealing sensitive information like PII and internal instructions.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/xu_xu_b2179aa8fc958d531d1/i-scanned-1-million-ai-services-heres-what-worries-me-more-than-the-vulnerabilities-1pi5 |
| Publication time | Mon, 25 May 2026 05:09:57 +0000 |
| Retrieval time | 2026-05-25T05:37:36.224Z |
| Last seen | 2026-05-25T05:37:36.224Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | VsY1FjNO_W-g |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3923210) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } xu xu Posted on May 25 I Scanned 1 Million AI Services. Here's What Worries Me More Than the Vulnerabilities #ai #security #llm #apidesign Your error rate just spiked 40%. Three weeks of debugging, two engineers on call rotation, and the coffee is cold. The terminal is still red. You're staring at a log that shows your AI service has been leaking embeddings to unauthorized requests for two weeks. Two weeks.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
