DIAGEO India A.I CyberSecurity Scoring
18/03/2026
Access Monitoring Plan
Access Monitoring Plan
No incidents recorded for DIAGEO India in 2026.
No incidents recorded for DIAGEO India in 2026.
No incidents recorded for DIAGEO India in 2026.
Latest updates, reports, and threat intel affecting the global network.
AI promises a major overhaul for India's finance sector, but widespread adoption faces significant hurdles from data infrastructure,...
After over 800 entries and multiple competitive rounds, World Class by Diageo has concluded its Regional Finals across India, Nepal and Sri...
The U.S. artificial intelligence sector witnessed an unprecedented funding surge in 2025. Fifty-five startups secured rounds exceeding $100...
In a reflective year-end note, Diageo India CEO Praveen Someshwar turns to nature, birdwatching and rural India to draw leadership lessons...
Dave Lewis will be responsible for steering the turnaround of the Johnnie Walker and Guinness maker, which recently downgraded its sales and...
Diageo's India arm will begin a strategic review of its investment in a unit which owns the Indian Premier League cricket team 'Royal...
Diageo India CEO Praveen Someshwar says the country is poised to become the world's most important consumer market, with the company betting...
The partnership aims to automate lifecycle access controls, continuously monitor access risk, and enforce policy across hybrid, multicloud,...
KOLKATA, Aug 2: This Friendship Day, House of McDowell's Soda is taking Yaari to new heights—both in the sky and on stage. As India's...
VaahCMS versions 2.0.0 through 2.3.4 contain a malicious obfuscated JavaScript payload embedded in the Blade template responsible for rendering security OTP emails, allowing remote attackers to execute unauthorized code in any browser that renders the affected email template with JavaScript enabled. The payload establishes a WebSocket connection to a hardcoded command-and-control endpoint, installs a password-field keylogger using MutationObserver to capture dynamically added inputs, scrapes WhatsApp Web DOM content, and accepts remote commands to redirect or overwrite the rendered page.
undici does not validate the type property of a duck-typed blob-like request body before using it as the Content-Type header on the HTTP/1.1 dispatcher. In undici before 6.28.0, from 7.0.0 up to before 7.29.0, and from 8.0.0 up to before 8.9.0, an application that passes a hand-rolled blob-like body (via request, stream, pipeline, or dispatch) whose type is derived from untrusted input allows an attacker to inject CRLF sequences and append arbitrary HTTP headers, potentially smuggling a second request past the upstream. Native Blob objects are safe because their constructor strips CRLF from the type, and fetch is unaffected because it validates headers, but ecosystem libraries that build duck-typed blob shapes from user input can reach the vulnerable path. This is the same defect class as CVE-2022-35948 and CVE-2026-1527, on a header sink that the earlier fixes did not cover. The issue is fixed in undici 6.28.0, 7.29.0, and 8.9.0.
undici's cache interceptor mishandles optional whitespace placed around the equals sign of a qualified no-cache or private Cache-Control directive. In undici from 7.0.0 up to before 7.29.0 and from 8.0.0 up to before 8.9.0, the parser either drops the directive or stores a field name with literal quote characters, so the cache decision fails to recognize the qualification and the response is stored. In shared-cache mode, this lets a response containing one user's authenticated data be served from cache to a later caller, including an unauthenticated one, when both requests resolve to the same cache key. It affects applications that enable the cache interceptor in shared mode, forward Authorization headers upstream, and receive cacheable responses with qualified directives padded with whitespace around the equals sign. This is the whitespace-around-equals variant that the fix for CVE-2026-9678 did not normalize, and it is fixed in undici 7.29.0 and 8.9.0.
kishan0725 Hospital Management System 4.0 is vulnerable to SQL Injection in check_availability.php via the parameters emailid and email.
kishan0725 Hospital Management System 4.0 is vulnerable to SQL Injection in /doctor/edit-patient.php?editid=1.
curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?
linkedin_id=axa' -H 'apikey: YOUR_API_KEY_HERE'
Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.
Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.