[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fLESADsBt9OUBJgvUEIta89UcQigijt7x1H5624M24To":3},{"article":4,"iocs":50,"watch_terms":59,"solutions":60,"lesson":153},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":27,"category":28,"article_tags":32},"15113804-070b-4ff4-882e-60caaa3dd263","Nearly 1 in 10 Exposed LiteLLM Gateways Accepted the Example \"sk-1234\" Admin Key","nearly-1-in-10-exposed-litellm-gateways-accepted-the-example-sk-1234-admin-key-fd5c4d","Nearly one in ten of the internet-facing LiteLLM servers that Wiz Research scanned in February accepted sk-1234, the example admin key in LiteLLM's own setup guide. LiteLLM is an open-source AI gateway, the software a company puts between its applications and the model providers it pays for. That key is the gateway's administrator credential. Anyone who holds it can read every","Wiz Research found that nearly 10% of internet-facing LiteLLM servers accepted the default 'sk-1234' admin key, which is documented in the setup guide. This key grants full administrative access, allowing attackers to steal API keys, access cloud IAM credentials, and potentially hijack AI model workloads. LiteLLM's security policy states that such configuration errors are out of scope for vulnerabilities.","Nearly 1 in 10 exposed LiteLLM gateways accepted the default 'sk-1234' admin key.","https:\u002F\u002Fthehackernews.com\u002F2026\u002F09\u002Fnearly-1-in-10-exposed-litellm-gateways.html","https:\u002F\u002Fblogger.googleusercontent.com\u002Fimg\u002Fb\u002FR29vZ2xl\u002FAVvXsEjfjbI1DXHJ4wQzSRFbddkmgQ9CTLSPPGP8fcQ6a37qbwKvgd4JxU51YhADR8S4IsWaiQ4fRApn-ih4m0AhsizM3wa6aJ3P8MlgBztNQm-oH4bE_TkPsmUZHhblcNMrQFxGdWnDHePCQDcSz-AJeWMoKH6YVcXXFCjK2ajZfbmObdeVkWmvv8O_fufqsl0\u002Fs1600\u002Flitellm.jpg","2026-09-10T07:12:55+00:00","2026-09-10T10:00:14.129183+00:00",8,[17,20,23,25],{"name":18,"type":19},"LiteLLM","product",{"name":21,"type":22},"AI gateway","technology",{"name":24,"type":22},"LLM",{"name":26,"type":19},"Shodan","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":27,"icon":29,"name":30,"slug":31},null,"Vulnerabilities","vulnerabilities",[33,35,40,45],{"category":34},{"id":27,"icon":29,"name":30,"slug":31},{"category":36},{"id":37,"icon":29,"name":38,"slug":39},"839da5c1-3c34-47e2-9499-f7201640e3ac","AI Security","ai-security",{"category":41},{"id":42,"icon":29,"name":43,"slug":44},"ade75414-7914-4e23-a450-48b64546ee70","Open Source","open-source",{"category":46},{"id":47,"icon":29,"name":48,"slug":49},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[51,55],{"type":52,"value":53,"context":54},"malware","sk-1234","Default example admin key for LiteLLM gateways.",{"type":56,"value":57,"context":58},"cve","CVE-2026-59821","Post-authentication code execution flaw in LiteLLM.",[18,26],{"controls":61,"vendors":149},[62,91,120],{"slug":63,"name":64,"problem":65,"products":66},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",[67,75,83],{"vendor_slug":68,"vendor_name":69,"vendor_logo":70,"product_slug":71,"product_name":72,"url":73,"description":74},"palo-alto-networks","Palo Alto Networks","\u002Fvendor-logos\u002Fpalo-alto-networks.png","idira-secrets-management","Idira Secrets Management","https:\u002F\u002Fwww.paloaltonetworks.com\u002Fidira\u002Fmachine\u002Fsecrets-management","Secrets management for applications, scripts and pipelines, from the former CyberArk portfolio.",{"vendor_slug":76,"vendor_name":77,"vendor_logo":78,"product_slug":79,"product_name":80,"url":81,"description":82},"gitguardian","GitGuardian","\u002Fvendor-logos\u002Fgitguardian.png","gitguardian-platform","GitGuardian Secrets Detection","https:\u002F\u002Fwww.gitguardian.com\u002F","Finds and helps remediate secrets leaked in repositories, CI pipelines and chat tools.",{"vendor_slug":84,"vendor_name":85,"vendor_logo":86,"product_slug":87,"product_name":88,"url":89,"description":90},"github","GitHub","\u002Fvendor-logos\u002Fgithub.png","advanced-security","GitHub Advanced Security","https:\u002F\u002Fgithub.com\u002Fsecurity\u002Fadvanced-security","Dependency review, code scanning and secret scanning with push protection.",{"slug":92,"name":93,"problem":94,"products":95},"attack-surface-management","External attack surface management (EASM)","You find your forgotten internet-facing systems before attackers do.",[96,104,112],{"vendor_slug":97,"vendor_name":98,"vendor_logo":99,"product_slug":100,"product_name":101,"url":102,"description":103},"recorded-future","Recorded Future","\u002Fvendor-logos\u002Frecorded-future.png","attack-surface-intelligence","Attack Surface Intelligence","https:\u002F\u002Fwww.recordedfuture.com\u002Fproducts\u002Fattack-surface-intelligence","External attack surface management that discovers internet-facing assets and prioritises their exposures.",{"vendor_slug":105,"vendor_name":106,"vendor_logo":107,"product_slug":108,"product_name":109,"url":110,"description":111},"watchtowr","watchTowr","\u002Fvendor-logos\u002Fwatchtowr.png","watchtowr-platform","watchTowr Platform","https:\u002F\u002Fwatchtowr.com\u002Fplatform\u002F","Continuous discovery of internet-facing assets, with automated testing for exploitable vulnerabilities.",{"vendor_slug":113,"vendor_name":114,"vendor_logo":115,"product_slug":116,"product_name":117,"url":118,"description":119},"censys","Censys","\u002Fvendor-logos\u002Fcensys.png","censys-external-exposure-management","Censys External Exposure Management","https:\u002F\u002Fcensys.com\u002Fsolutions\u002Fexternal-exposure-management","External attack surface discovery based on continuous internet-wide scanning.",{"slug":121,"name":122,"problem":123,"products":124},"cloud-security-posture","Cloud security posture management (CSPM and CNAPP)","Misconfigured cloud storage and over-permissive roles get caught before they leak.",[125,133,141],{"vendor_slug":126,"vendor_name":127,"vendor_logo":128,"product_slug":129,"product_name":130,"url":131,"description":132},"wiz","Wiz","\u002Fvendor-logos\u002Fwiz.png","wiz-cloud","Wiz Cloud","https:\u002F\u002Fwww.wiz.io\u002Fplatform\u002Fwiz-cloud","Agentless cloud security posture and attack path analysis across major cloud providers.",{"vendor_slug":134,"vendor_name":135,"vendor_logo":136,"product_slug":137,"product_name":138,"url":139,"description":140},"orca-security","Orca Security","\u002Fvendor-logos\u002Forca-security.png","orca-cloud-security-platform","Orca Cloud Security Platform","https:\u002F\u002Forca.security\u002Fplatform\u002F","Agentless cloud security platform for posture, vulnerabilities and data exposure.",{"vendor_slug":142,"vendor_name":143,"vendor_logo":144,"product_slug":145,"product_name":146,"url":147,"description":148},"microsoft","Microsoft","\u002Fvendor-logos\u002Fmicrosoft.png","defender-for-cloud","Microsoft Defender for Cloud","https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fsecurity\u002Fbusiness\u002Fcloud-security\u002Fmicrosoft-defender-cloud","Cloud posture management and workload protection for Azure, AWS and Google Cloud.",[150],{"slug":126,"name":127,"logo_path":128,"roles":151},[152],"reported_by",{"slug":154,"title":155,"body":156,"framework_refs":157,"framework_notes":168},"default-admin-key-exposes-nearly-10-of-public-litellm-ai-gateways","Default Admin Key Exposes Nearly 10% of Public LiteLLM AI Gateways","Nearly one in ten internet-facing LiteLLM deployments accepted the example admin key 'sk-1234' straight from the documentation, granting attackers full administrative access without any exploitation of a software vulnerability. This represents a fundamental configuration management failure: organizations deployed production AI infrastructure using credentials explicitly marked as examples, not secrets. The consequences are severe — attackers can exfiltrate downstream API keys, harvest cloud IAM credentials, and hijack AI model workloads entirely. This incident highlights that as AI tooling proliferates rapidly, security hygiene fundamentals are being overlooked, and vendors disclaiming responsibility for default-credential misuse does not reduce real-world risk.",[158,159,160,161,162,163,164,165,166,167],"CIS Control 4: Secure Configuration of Enterprise Assets and Software","CIS Control 5: Account Management","CIS Control 12: Network Infrastructure Management","NIST SP 800-53 IA-5: Authenticator Management","NIST SP 800-53 CM-6: Configuration Settings","NIST SP 800-53 AC-17: Remote Access","NIST CSF PR.AC-1: Identities and credentials are managed","OWASP Top 10 A05:2021 – Security Misconfiguration","OWASP Top 10 A07:2021 – Identification and Authentication Failures","GDPR Article 32: Security of Processing (appropriate technical measures)",{}]