
Camille's Sidewalk Cafe
None



None

On Aug. 8, 1950, an adventurous and determined entrepreneur named Harmon Dobson opened up the world’s first Whataburger on Ayers Street in Corpus Christi, Texas. He had a simple goal: to serve a burger so big it took two hands to hold and so good that after one bite customers would say, “What a burger!” He succeeded on both counts and turned that one little burger stand into a legend loved throughout Texas and the South. Today, each and every Whataburger is made to order, right when it’s ordered. And they’re still made with 100 percent pure, never-frozen beef and served on a big toasted five-inch bun with all “the extras” to suit your taste. Grilled jalapeños, extra bacon, three slices of cheese, no tomatoes, extra pickles? No problem. Your Whataburger will be made just like you like it, 24 hours a day, seven days a week. Whataburger’s following has grown exponentially in its more than 75-year history, thanks to a number of features, including its famous burgers and growing list of menu items, its iconic orange-and-white-striped restaurants and its famous Fancy Ketchup. Whataburger is more than a burger chain. It’s a place that feels like home to more than 51,000 employees, called Family Members, and millions of customers. It’s a brand built on pride, care and love. It’s a place people count on in their communities. It’s a place where goodness lives. So now with more than 1,100 Whataburger restaurants across 16 states stretching from Las Vegas to the Carolinas, road-trippers and hometown folks alike continue gathering under the big orange-and-white roofs for fresh, made-to-order burgers and friendly service.
Security & Compliance Standards Overview












No incidents recorded for Camille's Sidewalk Cafe in 2026.
No incidents recorded for Whataburger in 2026.
Camille's Sidewalk Cafe cyber incidents detection timeline including parent company and subsidiaries
Whataburger cyber incidents detection timeline including parent company and subsidiaries
Last 3 Security & Risk Events by Company
nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.
PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.
PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.
PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.
PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.