Search/gitlab
● Vendor

gitlab

Known CVEs
0
Highest CVSS
—
In KEV
0
Vendor
gitlab
Connections
241 relationships
Week in review: Records allegedly stolen from Azure tenants, Medusa ransomware hits 500+ orgs
Week in review: Records allegedly stolen from Azure tenants, Medusa ransomware hits 500+ orgs Here’s an overview of some of last week’s most interesting news, articles, interviews and videos: Windows 11’s strongest security defenses can be bypassed without a screwdriver Researchers from the University of Birmingham and Durham University have found a way to knock down some of the toughest protections in Windows 11 without physically opening or modifying the target machine. The attack assumes the attacker has already gained privileged access to the system. Police bust cybercrime ring accused of stealing €30 million in four-day spree German and Brazilian police dismantled an international bank fraud ring blamed for a €30 million cyberattack on a German financial institution, arresting four people in Brazil and pursuing three more suspects in Spain and Bulgaria. SafePal breach affects 39,798 customers, data allegedly for sale Cryptocurrency wallet maker SafePal disclosed a data breach that exposed order information for 39,798 customers, including names, email addresses, shipping addresses, phone numbers and purchase details. The company traced the exposure to an authorization flaw in a plug-in used for order tracking. Under certain conditions, the flaw let one customer view another customer’s order information. Attackers exploit patched macOS Screen Sharing flaw to deploy cryptominer A recently patched security flaw in Apple macOS is being actively exploited by hackers to bypass authentication, gain root access, and install a cryptominer, the Netherlands’ National Cyber Security Centre (NCSC) warns. France’s tax authority admits hackers made off with data on 678,000 individuals France’s tax authority has disclosed a data breach after an attacker accessed the General Directorate of Public Finances (DGFiP) systems, saying the intrusion exposed data on 678,000 individuals and professionals. The incident came to light after an alleged attacker using the alias “ZeroBytes” took credit on a cybercrime forum and listed a stolen database for sale. Hacker claims millions of records stolen from corporate Azure tenants A threat actor known as “TheHatman” claims to have obtained millions of employee records from the Azure environments of several Fortune 500 companies, including McDonald’s, Vodafone, Kyndryl, and Tata Consultancy Services (TCS), according to Hudson Rock. Critical GitLab flaw allows attackers to modify or delete public projects (CVE-2026-19478) GitLab has released patches for two vulnerabilities, including a critical-severity code injection flaw that can be exploited without authentication. The vulnerabilities affect GitLab Community Edition (CE) and Enterprise Edition (EE) versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4. ChatGPT’s new feature could give infostealers a map of your Mac activity OpenAI’s new Computer History feature turns recent Mac computer activity into memories ChatGPT and Codex can use, and it’s raising questions about privacy and security along the way. Computer History builds a timeline out of everyday computer use, grouping activity into summaries and noting which apps and websites contributed to each one. Cyberattack forces UT San Antonio to delay start of fall semester The University of Texas at San Antonio pushed back the start of its fall semester by three days after a cyberattack targeted its academic network over the weekend. Classes that were due to begin on Wednesday, August 19 will now start on Monday, August 24. Google’s AI security agents found 100+ critical software vulnerabilities in just two days Google’s Mandiant has disclosed the workings of an internal tool that uses chains of AI agents to hunt for vulnerabilities in source code, saying it found over 100 verified, high-severity flaws in just two days during a live investigation into stolen corporate repositories. Medusa ransomware gang has hit over 500 organizations, CISA warns Medusa ransomware has breached more than 500 organizations since it first appeared in June 2021, the FBI, CISA, and the Department of Health and Human Services (HHS) said in an updated joint advisory. The update builds on an advisory first issued in March 2025 and draws on FBI investigations conducted as late as April 2026. Researchers find a loophole that lets expired credit cards make unauthorized payments A team from the University of Massachusetts Amherst has shown that a contactless credit card keeps working past its printed expiration date, even after the cardholder gets a replacement. They named it the Zombie Card attack and presented the findings at USENIX Security 2026. US charges 17 Iranian hackers over 31-terabyte academic data theft The U.S. has charged 17 alleged members of Mabna Institute, an Iranian hacking-for-hire company accused of running a years-long campaign that stole data from American universities, companies, and government agencies. The Southern District of New York case adds eight names to the nine already charged back in 2018. US agencies warn of AI-powered attacks on Siemens industrial controllers Threat actors are using AI to write exploit scripts targeting internet-exposed Siemens S7 Series programmable logic controllers (PLCs) used across water, energy, manufacturing, and other critical infrastructure sectors, according to US federal agencies. Fake Gemini installer delivers Vidar infostealer via Google Colab lure A malicious executable masquerading as a Google Gemini installer was used to deliver the Vidar infostealer on a company network in the EMEA region, according to Darktrace researchers who investigated the incident. A $25 template helped scammers build hundreds of phantom bank domains A phrase on a suspicious website turned into an investigation of phantom banks built to support scams, according to new research from Allure Security. Molly DeQuattro, the company’s VP of Operations, was reviewing a domain that resembled the brand of one of its financial services clients. The page carried none of that client’s branding. It presented an unrelated bank instead. Citrix urges customers to fix critical NetScaler authentication bypass (CVE-2026-19490) Citrix has patched two vulnerabilities in NetScaler ADC and NetScaler Gateway, including a critical authentication bypass flaw tracked as CVE-2026-19490, and is urging customers to upgrade affected appliances as soon as possible. Attackers impersonate popular AI brands to spread malware Attackers are impersonating popular AI brands like Perplexity, Claude, ChatGPT, and Copilot to spread information stealers, backdoors, malicious browser extensions, and other malware, according to Sophos. Critical Microsoft Entra ID vulnerability exploited in the wild (CVE-2026-69836) Microsoft has patched a critical remote code execution vulnerability (CVE-2026-69836) in Entra ID, reportedly exploited in the wild. Entra ID is Microsoft’s cloud identity service, formerly Azure Active Directory, that verifies logins and controls access to Microsoft 365, Azure, and connected third-party apps. A hollowed out data layer is making CISOs fly blind into AI attacks The security industry is currently transitioning to an era where both offense and defense are AI-led, and every SOC operates at machine speed. However, what most CISOs have not yet reckoned with is that the AI defenders they are about to deploy will inherit a data foundation that two years of ingestion cost pressure has quietly hollowed out. The result is a security industry heading into an AI era with less visibility than it had five years ago. Download: 2026 Credential Risk Report 85% of cybersecurity professionals consider compromised credentials a primary attack path—yet only 19% continuously monitor active credentials and automatically remediate exposure. The 2026 Credential Risk Report examines where credential security programs fall short and what it takes to move toward Continuous Credential Defense. When companies get specific about AI, revenue growth looks different Companies that provide specific evidence of how they use AI tend to record stronger revenue growth. Researchers at Carnegie Mellon University and Larridin examined a study universe of 564 companies across 12 industry sectors. Individual analyses used smaller samples depending on data availability. Product showcase: ScamNet looks for warning signs in suspicious calls and shady links ScamNet: Anti-Scam Suite is a consumer security app from Synaptrex Technologies that helps users detect and block scams involving phone calls, text messages, websites, and other suspicious content. The app is available for iPhone, iPad, and Mac, with features varying by platform. Call protection is available on iPhone, while tools such as Visual Intelligence are supported on iPhone and iPad. The app is free with optional ScamNet+ subscriptions. Hazmat: Open-source containment for AI agents Hazmat is an open-source tool that runs AI coding agents inside a separate account on your own machine. It wraps the harnesses people use: Claude Code, Codex, OpenCode, Cursor Agent, and several more, plus any script you write yourself. Attackers turn to AI for help identifying files worth stealing AI tools are being used by cyber attackers to write malicious code, build tools that harvest credentials, search compromised networks, identify valuable business information, manage technical infrastructure and generate commands during intrusions. Gambit Security researchers examined three unrelated threat actors that show how AI can support different stages of a cyberattack. Google’s open-source HEIR lets AI work with data it can’t see Google’s researchers and engineers developed the Homomorphic Encryption Intermediate Representation (HEIR) compiler project, an open-source compiler toolchain and development platform for homomorphic encryption. It can convert pre-trained AI models designed to operate on unencrypted data into models that process encrypted inputs. OpenAI tightens defenses after AI agents breach research environment Following the OpenAI-Hugging Face incident, in which an agentic collective autonomously penetrated OpenAI’s research infrastructure and another company’s production infrastructure by chaining together multiple weaknesses, OpenAI began strengthening its safety requirements. The weaknesses included previously unknown vulnerabilities and credentials leaked online. Google’s $10,000 refund test shows why AI agents need zero trust Google’s open-source autonomous Customer Support & Returns Agent, built using the Agent Development Kit (ADK) and Gemini, demonstrates how developers can apply zero-trust security principles to AI agents that interact with sensitive systems and take real-world actions. Banks look for fraud signals in customer behavior Banks are dealing with more fraud in which customers authorize payments after being manipulated by criminals. ThreatMark’s Fraud Readiness Benchmark 2026 describes a banking environment where social engineering, reimbursement requirements and growing case volumes are changing fraud operations. OpenAI puts major frontier AI training run on hold over cyber risks OpenAI temporarily paused reinforcement learning (RL) training on its latest models intended for deployment for two weeks while it hardened and red-teamed research environments and expanded monitoring. The move followed the OpenAI-Hugging Face incident and preliminary evidence that the company’s upcoming Astra model may meet the Critical cybersecurity capability threshold under its Preparedness Framework. 8,539 reasons to rethink how vulnerabilities get patched The window for responding to newly disclosed security flaws is getting shorter. Exploit code can appear quickly, exploitability can be tested soon after disclosure, and organizations have a growing number of weaknesses to sort through. Rapid7’s Q2 2026 Threat Landscape Report counted 8,539 high- and critical-severity vulnerability disclosures, twice the number recorded a year earlier. AI is making fraud harder to spot and identity harder to prove Online fraud has become a routine concern for consumers and businesses that rely on digital accounts, payments and customer service. Experian’s 2026 U.S. Identity & Fraud Report describes a market where scams extend across messages, websites, documents, voices, images and account activity. OpenAI previews privacy-focused system for detecting AI misuse OpenAI is previewing Private Safety Processing with early customers seeking greater certainty about how their data will be protected as AI systems become more capable. The system identifies patterns across related interactions while restricting OpenAI personnel from accessing the underlying content. The company plans to start rolling it out and publish a technical white paper in September. AWS limits AI agents’ data access, even when manipulated AWS has detailed an approach for propagating user authorization context through AI agents, allowing access controls to be enforced by infrastructure and downstream services rather than relying on the agent itself. Nearly half of enterprises have no one leading PQC migration Enterprises believe they are prepared for the security challenges posed by quantum computing, but gaps in ownership, testing and visibility could complicate their transition to post-quantum cryptography (PQC), according to new research from Axiad. Cybersecurity jobs available right now: August 18, 2026 We’ve scoured the market to bring you a selection of roles that span various skill levels within the cybersecurity field. Check out this weekly selection of cybersecurity jobs available right now. New infosec products of the week: August 21, 2026 Here’s a look at the most interesting products from the past week, featuring releases from F5 Networks, Intezer, Netscout, and Tufin.
helpnetsecurity.comAug 23, 2026extracted
Microsoft Patches Exploited Entra ID Vulnerability
Microsoft on Thursday announced the rollout of 22 new security updates that resolve severe vulnerabilities across multiple products, including a critical Entra ID zero-day exploited in attacks. The exploited Entra ID flaw is tracked as CVE-2026-69836, and it could have been exploited for remote code execution (RCE). Microsoft discovered the issue internally and patched it on the server side, with no action required from customers. The tech giant has not shared any information about the attacks involving exploitation of CVE-2026-69836. Most of the other patches address critical and high-severity flaws in Microsoft Azure, Entra ID, Exchange, Fabric, and Partner Center products. The most severe of these include elevation-of-privilege (EoP) bugs in Azure SQL Database (CVE-2026-69502), Azure Arc (CVE-2026-69555 and CVE-2026-65816), and Exchange Online (CVE-2026-65801), as well as an RCE flaw in Azure Managed Instance for Apache Cassandra (CVE-2026-65770), all with a CVSS score of 10/10. Seven other critical EoP issues were resolved: CVE-2026-68782 (Azure SQL Database), CVE-2026-63509 (Microsoft Fabric), CVE-2026-69851 (Entra ID), CVE-2026-68789 (Azure SQL Database), CVE-2026-69400 (Azure Logic Apps), CVE-2026-62834 (Azure Data Factor), and CVE-2026-66309 (Azure SQL Database). Additionally, Microsoft patched high-severity vulnerabilities in Azure Virtual Machines, Microsoft Partner Center, Azure Data Factory, Azure Stack HCI, Azure Data Manager for Energy, Copilot in Azure, and Windows Remote Help Defense. No customer action is required for the majority of these security defects, as Microsoft has deployed the mitigations on the server side. Earlier this week, Microsoft fixed a high-severity command injection bug in Copilot that could be exploited remotely for information disclosure (CVE-2026-24301). Last week, the company announced that it was working on patches for ShieldBreak, a zero-day Defender exploit dropped on August 2026 Patch Tuesday by security researcher Nightmare Eclipse (also known as Chaotic Eclipse). The company assesses that the vulnerability ShieldBreak targets is a high-severity bug, now tracked as CVE-2026-69414 (CVSS score of 7.8). “Microsoft is aware of an elevation of privilege in the Microsoft Malware Protection Engine in Microsoft Defender publicly referred to as ‘ShieldBreak’. We are working to provide a high-quality security update that addresses this vulnerability,” the company said. Headline and body of the article have been updated to show that the Entra ID vulnerability has been exploited Related: CISA Urges Immediate Patching of Exploited TrueConf Vulnerabilities Related: Critical GitLab Flaw Exploited Shortly After Disclosure
securityweek.comAug 21, 2026extracted
GitLab 19.3 helps enterprises scale agentic development securely
GitLab 19.3 helps enterprises scale agentic development securely GitLab has announced updates that give enterprises more control as they scale agentic software development. GitLab Dedicated customers, who already run their most sensitive software delivery workloads on GitLab, can now run GitLab Duo Agent Platform inside that same single tenant environment and region, connect their own models for inference, and keep AI-processed data inside their existing security boundary. GitLab 19.3 also ships today with support for Secrets Manager, Flow Creator Agent, and Bulk SAST False Positive Detection and Agentic SAST Vulnerability Resolution. Every secret, whether it’s used inside a pipeline or by the infrastructure outside the pipeline, now runs under the same permission model. Additionally, developers who own a process can now create custom agentic flows across the software development lifecycle, and security teams can ship ready-to-merge fixes against their backlog at scale. Together, these updates give engineering teams, process owners, and security teams the speed of agentic AI, without giving up the control they already have in place. “These updates extend the speed and control enterprises need deeper into the regulated and data-sensitive segment of the enterprise market,” said Manav Khurana, chief product and marketing officer at GitLab. “Every capability we shipped this month, from where an agent runs to which secret it can touch, extends that same control into the trusted software delivery workflows enterprises already depend on.” Dedicated AI Gateway keeps agentic AI inside trusted boundaries The AI Gateway for GitLab Duo Agent Platform now runs inside GitLab Dedicated single-tenant SaaS infrastructure, enabling agentic workloads to follow the same residency and isolation model as the rest of the software development lifecycle within GitLab. Regulated and residency-sensitive teams can unlock the use of agentic AI for software delivery under the same deployment model their auditors already understand. Secrets Manager extends control beyond the pipeline GitLab Secrets Manager is now in limited availability as a paid add-on billed through GitLab Credits for GitLab.com customers. Every CI secret is scoped to the environment, branch, and protection status of the job that needs it. Secrets Manager also now supports Kubernetes, Terraform, OpenTofu, and custom tools. Credentials live in the same platform that runs code and pipelines, so teams do not maintain a separate permission model. Bulk SAST remediation Helps remove years of accumulated risk in a single action SAST False Positive Detection and Agentic SAST Vulnerability Resolution enable teams to clear an entire vulnerability backlog instead of one finding at a time. Teams select multiple findings in the Vulnerability Report, and GitLab returns a confidence score for each. Confirmed risks get a ready-to-merge fix, so a developer reviews and merges instead of writing the fix from scratch. This covers every SAST vulnerability in the Vulnerability Report, and GitLab continues to triage and remediate new critical and high severity findings automatically as they arrive. Flow Creator Agent removes the schema barrier to custom automation Flow Creator Agent removes the need for manual schema mapping that keeps process owners from automating their work. With Flow Creator, available through Agentic Chat as a foundational agent in GitLab Duo Agent Platform, a user describes the automation in plain language and gets back a complete, runnable flow, ready to register from the AI Catalog. Every flow still runs under a scoped service account with composite identity, requiring the Maintainer role or higher to enable it. Additional capabilities shipped in GitLab 19.3 GitLab Credits usage caps are now generally available, allowing organizations to set a monthly ceiling on agentic AI spend before it becomes an overage. Administrators can set a subscription level cap in the Customers Portal, along with options for a default per user cap or per user overrides through the GraphQL API. Restricted visibility for custom agents and flows per GitLab group is now generally available, making them accessible to members across multiple projects within that group. This is in addition to per-project and public visibility options that have already been available.
helpnetsecurity.comAug 21, 2026extracted
GitLab CVE-2026-19478 Comes Under Active Exploitation Within Days of Disclosure
A newly disclosed security flaw in GitLab has come under active exploitation within days of public disclosure, according to watchTowr. The vulnerability in question is CVE-2026-19478 (CVSS score: 9.4), a case of code injection that allows an unauthenticated attacker to modify or delete publicly accessible GitLab projects and rewrite their data under certain conditions without requiring credentials, user interaction, or obscure configuration. The following versions of GitLab Community Edition (CE) and Enterprise Edition (EE) are affected by the flaw - 18.2 before 18.11.11 19.0 before 19.0.8 19.1 before 19.1.6 19.2 before 19.2.4 In an alert released earlier this week, GitLab said the issue could be exploited via a GraphQL directive. Fixes for the flaw were rolled out in GitLab CE and EE versions 19.2.4, 19.1.6, 19.0.8, and 18.11.11. Preemptive exposure management firm watchTowr told The Hacker News that it was able to reproduce the vulnerability within minutes of its disclosure, adding that it observed in-the-wild exploitation against its honeypot network. "This is the new reality of vulnerability reproduction and exploitation, where AI [artificial intelligence]-enabled attackers are able to compress the time from disclosure to exploitation and 'waiting until the next patch cycle' is often too late," Jake Knott, principal security researcher at watchTowr, said. "Organizations that haven't patched yet should hunt through web logs for requests containing '@gl_introduced,' and look for signs of probes or attempted exploitation." watchTowr also noted that the vulnerability's impact goes beyond the ability to modify or delete public projects, adding "an attacker can delete entire repositories, forge merge records to make it appear as if a fix landed when it didn't, and ban project maintainers." The development once again highlights how AI is rapidly changing the speed and the scale of the attacks, making it crucial that users apply the updates in a timely fashion. Organizations running internet-facing self-hosted GitLab instances should prioritize upgrading to a patched release. If immediate patching is not possible, it's advised to restrict unauthenticated access to "/api/graphql", or remove public repository access entirely as a mitigation.
thehackernews.comAug 21, 2026extracted
Hackers Target Zimbra Servers in Active Exploitation Campaign
A recently patched Zimbra Collaboration vulnerability is being exploited in the wild, according to Poland’s CERT Polska. The security hole is tracked as CVE-2026-73570 and it was patched by the developers of the enterprise email server and collaborative software suite with the release of version 10.1.20, announced on July 20. The high-severity flaw exists when the optional ‘zimbra-snmp’ package is installed and SNMP notifications are enabled. An attacker can exploit the vulnerability without authentication to execute arbitrary OS commands as the Zimbra user. The Polish CERT announced seeing attacks this week but did not share any details about the active exploitation campaign. It did, however, share some indicators of compromise (IoCs). The threat actor behind these attacks and its motivation remain unclear. However, these vulnerabilities can allow threat actors to gain full control of a targeted Zimbra server. The hackers can then establish persistence, access email accounts, harvest credentials, and move laterally to other systems. CISA’s KEV catalog currently includes 18 Zimbra Collaboration Suite vulnerabilities, including four added this year. CVE-2026-73570 has yet to be added to the catalog. Exploitation of Zimbra vulnerabilities has frequently been linked to Russian and Chinese state-sponsored hackers targeting military and diplomatic intelligence, as well as opportunistic cybercriminals seeking financial gain. Related: MLflow Vulnerability Exploited for Cloud Credential Theft Related: Critical GitLab Flaw Exploited Shortly After Disclosure
securityweek.comAug 20, 2026extracted
MLflow Vulnerability Exploited for Cloud Credential Theft
Threat actors have been exploiting a recent MLflow vulnerability to steal sensitive information, including credentials and secrets. An open source AI engineering platform, MLflow allows users to manage the end-to-end machine learning lifecycle and deploy AI agents, LLMs, and ML models in production. It has over 27,000 GitHub stars and more than 60 million monthly downloads. Tracked as CVE-2026-64849 (CVSS score of 9.3), the exploited security defect is described as an unauthenticated server-side request forgery (SSRF) issue that allows attackers to send HTTP requests to internal endpoints. The issue exists because the default MLflow Tracking Server (mlflow server) exposes the model-registry webhooks API without authentication, according to MLflow’s advisory. One of the exposed endpoints would return the upstream response status and body to the caller, and an SSRF protection that was added in version 3.10.0 could be bypassed. “Attackers are exploiting the vulnerability to reach cloud metadata services directly and exfiltrate cloud credentials and secrets,” attack surface management firm WatchTowr warns. According to the company, in-the-wild exploitation started within hours of CVE assignment, targeting cloud-hosted instances. “All MLflow versions before 3.15.0 are affected. If your organization runs MLflow, prioritize patching any exposed systems, review audit logs for signs of compromise, and check whether sensitive credentials may have been exposed,” WatchTowr says. On Wednesday, the US cybersecurity agency CISA added CVE-2026-64849 to its Known Exploited Vulnerabilities (KEV) catalog, urging federal agencies to patch it within two weeks, in line with BOD 26-04’s recommendations. Related: Cisco Patches Critical Crosswork, Secure Workload Vulnerabilities Related: Critical GitLab Flaw Exploited Shortly After Disclosure Related: Chrome, Firefox Updates Patch Dozens of Vulnerabilities
securityweek.comAug 20, 2026extracted
Cisco Patches Critical Crosswork, Secure Workload Vulnerabilities
Cisco on Wednesday announced patches for 15 vulnerabilities across its products, including critical- and high-severity flaws in Crosswork and Secure Workload. Crosswork version 7.2.1-SP was released with fixes for four critical-severity CVEs. Three of them, CVE-2026-20030, CVE-2026-20357, and CVE-2026-20358, have a maximum severity rating (CVSS score of 10/10), while the fourth, CVE-2026-20359, has a near-max severity (CVSS score of 9.9/10). According to Cisco, each CVE groups multiple issues under the same underlying vulnerability class. The first three are SQL injection, missing authentication, and external control of file system issues, while the fourth includes insufficient protection of credentials. Successful exploitation of these security defects could potentially allow attackers to mount remote code execution (RCE), authentication bypass, path traversal, and file overwrite/deletion attacks. On Wednesday, Cisco rolled out Secure Workload versions 4.0.4.16 and 3.10.9.1 with fixes for five CVEs that also group multiple issues, including four with a ‘critical’ severity rating. CVE-2026-20315 and CVE-2026-20317 cover improper access control and authentication bugs potentially leading to bypasses; CVE-2026-20231 groups code/OS command injections; and CVE-2026-20318 covers input validation and path traversal issues. The fifth CVE covers buffer overflows and out-of-bounds write issues, collectively tracked as CVE-2026-20319. Cisco also resolved a high-severity security defect in the Open Client Interface (OCI) XML parser of BroadWorks that could be exploited remotely without authentication to read sensitive configuration information. Tracked as CVE-2026-20320, it existed because external entity resolution was allowed by default, allowing attackers to send crafted XML messages and view sensitive files with BroadWorks user privileges. The flaw was resolved in version RI.2026.07 of BroadWorks Application Delivery Platform, BroadWorks Application Server, BroadWorks Profile Server, and BroadWorks Xtended Services Platform. Additionally, the company rolled out fixes for medium-severity weaknesses in Unified Intelligence Center, RoomOS, Industrial Ethernet (IE) 1000 series switches, and Packaged Contact Center Enterprise (CCE) and Unified Contact Center Enterprise (CCE). Cisco says it is not aware of any of these vulnerabilities being exploited in the wild. Additional information can be found on the company’s security advisories page. Related: Critical GitLab Flaw Exploited Shortly After Disclosure Related: Hackers Using AI to Target Siemens PLCs in Critical US Sectors
securityweek.comAug 20, 2026extracted
Exploitation Expected for Critical Authentication Bypass Patched in Citrix NetScaler
Citrix on Wednesday announced patches for two vulnerabilities in NetScaler ADC and NetScaler Gateway, including a critical-severity flaw. The critical bug, tracked as CVE-2026-19490 (CVSS score of 9.3), is described as an authentication bypass using an alternative path, and impacts NetScaler appliances configured as a gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy) or an AAA virtual server. It can be exploited by remote, unauthenticated attackers without user interaction, cybersecurity firm Rapid7 says. Per Citrix’s advisory, the security defect impacts NetScaler ADC and NetScaler Gateway versions 14.1-43.56 or later, 14.1-66.68-FIPS or later, 14.1-43.55 or earlier, 13.1-61.28 or later, 13.1-61.27 or earlier, and 13.1 FIPS. NetScaler ADC and Gateway versions 14.1-73.32, 13.1-63.21, 14.1-73.32 FIPS, and 13.1-FIPS and 13.1-NDcPP 13.1-37.277 contain fixes for this flaw and for CVE-2026-19489, a high-severity memory overflow issue that could lead to unexpected behavior or denial-of-service (DoS) if SIP ALG is enabled at an LSN group configuration. “Secure Private Access Hybrid deployments using NetScaler instances are also affected by the vulnerabilities. Customers need to upgrade these NetScaler instances to the recommended NetScaler builds to address the vulnerabilities,” Citrix says. According to Rapid7, there are no indicators that threat actors are exploiting the authentication bypass issue, but NetScaler’s critical role within enterprise systems makes it an attractive target for hackers. “NetScaler ADC and NetScaler Gateway are widely deployed enterprise networking products commonly positioned at or near the network perimeter. NetScaler ADC provides application delivery, traffic management, load balancing, SSL/TLS offloading, and application security capabilities, while NetScaler Gateway provides secure remote access and VPN functionality,” the cybersecurity firm notes. Rapid7 expects threat actors to exploit the critical bug shortly, given that NetScaler appliances are typically deployed in enterprise DMZs and are publicly accessible. “Organizations should prioritize patching affected systems on an emergency basis, since Citrix products are high-value targets that tend to quickly see exploitation in the wild,” the company says. Related: Critical GitLab Flaw Exploited Shortly After Disclosure Related: Citrix Patches NetScaler Vulnerabilities, Including New ‘HTTP/2 Bomb’ Attack Related: Exploitation of Fresh Citrix NetScaler Vulnerability Begins Related: 943 Patches Rolled Out With Oracle’s August 2026 Security Update
securityweek.comAug 20, 2026extracted
Critical GitLab Flaw Exploited Shortly After Disclosure
Threat actors started exploiting a critical-severity GitLab vulnerability roughly two days after public disclosure, attack surface management company WatchTowr warns. Tracked as CVE-2026-19478 (CVSS score of 9.4), the code injection defect was patched on August 17, when GitLab warned that it could be exploited remotely without authentication. “GitLab has remediated an issue that under certain conditions could allow an unauthenticated user to remotely modify or delete public projects and user data via a GraphQL directive,” GitLab said. Fixes were rolled out in GitLab Community Edition (CE) and Enterprise Edition (EE) versions 19.2.4, 19.1.6, 19.0.8, and 18.11.11. On August 18, WatchTowr warned that the flaw could be easily reproduced, urging users to update their self-managed instances as soon as possible. As a mitigation, they should restrict unauthenticated access to the /api/graphql endpoint or remove public repository access entirely. “Whilst no public exploit code is available, WatchTowr was able to reproduce the vulnerability within minutes of its disclosure, armed only with the advisory details and patch. AI-enabled attackers are unlikely to be far behind,” the company told SecurityWeek at the time. On Wednesday, WatchTowr warned that its honeypot network has already caught the first in-the-wild exploitation attempts targeting CVE-2026-19478. “Organizations that haven’t patched yet should hunt through web logs for requests containing ‘@gl_introduced’, and look for signs of probes or attempted exploitation,” the company said. The narrow patch window, fueled by the bug’s severity and the use of AI, is the new reality of vulnerability reproduction and exploitation, WatchTowr principal security researcher Jake Knott points out. “The newly disclosed code injection vulnerability allows an unauthenticated attacker to delete publicly accessible GitLab projects and rewrite their state, deleting repositories entirely, forging merge records, or banning maintainers in a single HTTP request with no credentials, user interaction, or obscure configuration required,” Knott says. According to Mondoo co-founder and CSO Patrick Münch, the fresh GitLab defect could easily fuel the next wave of supply chain attacks, given that it can be exploited to forge any merge records. “Think about what that means. In every supply chain worm we’ve tracked this year, attackers had to work around code review, because faking an approval was harder than dodging it. This does it for free. An attacker can make a malicious change look reviewed and signed off by someone your team trusts, your pipeline builds it and ships it downstream, and your own audit log swears the whole thing was legitimate. Deleting a repo costs you a bad afternoon. Forging trust in it costs you every release that follows,” Münch said. Related: 943 Patches Rolled Out With Oracle’s August 2026 Security Update Related: Chrome, Firefox Updates Patch Dozens of Vulnerabilities Related: Trivy, Not LiteLLM Behind the 2,500 Org Compromise
securityweek.comAug 20, 2026extracted
Chrome, Firefox Updates Patch Dozens of Vulnerabilities
Google and Mozilla on Tuesday announced fresh Chrome and Firefox security updates that address multiple critical- and high-severity vulnerabilities. Firefox 154 was released to the stable channel with patches for 58 CVEs, including 20 high-severity flaws, roughly half of which are memory safety bugs that could be exploited for code execution. Resolved high-severity issues include six use-after-free defects, six privilege escalation vulnerabilities, two information disclosure bugs, one sandbox escape flaw, one site isolation issue, and one mitigation bypass weakness. Per Mozilla’s advisory, the update also resolves multiple internally discovered bugs leading to memory corruption and other security-related defects that could have been exploited. They were collectively assigned three CVEs. On Tuesday, Mozilla also announced the rollout of Thunderbird 154 with patches for 55 vulnerabilities. Firefox ESR 115.39, Firefox ESR 140.14, Firefox ESR 153.1, Thunderbird 140.14, and Thunderbird 153.1 were also released with fixes for dozens of these security defects. Google released a fresh Chrome 151 update that resolves 15 vulnerabilities, including two critical-severity buffer overflow bugs in WebGL and Dawn. The remaining 13 flaws are high-severity inappropriate implementation, link following, race condition, incorrect reference resolution, use-after-free, use of uninitialized resource, buffer overflow, incorrect calculation, information leak, and type confusion issues. Google says it found 11 of these security defects, while the other four were discovered and reported by external researchers. The company has yet to disclose the bug bounty amounts to be paid. The latest Chrome release is now rolling out to users as versions 151.0.7922.169/.170 for Windows and macOS, and as version 151.0.7922.169 for Linux. Related: AI-Driven Vulnerability Surge Breaks the Traditional Patching Model Related: 300,000 WordPress Sites Potentially Exposed to Hacking Due to Form Plugin Flaw Related: GitLab Patches Critical Code Injection Vulnerability Related: Dozens of WebKit Vulnerabilities Patched With Fresh macOS, iOS Security Updates
securityweek.comAug 19, 2026extracted
NCSC-2026-0305 [1.00] [M/H] Kwetsbaarheden verholpen in Mattermost
Mattermost, Inc. heeft kwetsbaarheden verholpen in Mattermost versies 10.11.x, 11.7.x en 11.8.x, inclusief de GitLab plugin tot versie 11.8. De kwetsbaarheden betreffen meerdere aspecten van de Mattermost software, waaronder onjuiste validatie van WebSocket command velden, onjuiste reconciliatie van SchemeAdmin flags, en onvoldoende verificatie van kanaaleigendom bij ABAC policy unassign endpoints. Hierdoor kunnen geauthenticeerde gebruikers onder andere denial-of-service veroorzaken door het laten crashen van plugin processen, administratieve privileges behouden na demotie, en ongeautoriseerde wijzigingen aanbrengen in toegangscontrolebeleid en board-rollen. Verder kunnen guest gebruikers via speciaal vervaardigde boardarchiefbestanden hun privileges escaleren naar Board Admin. OAuth applicaties kunnen tokens en autorisaties van andere integraties intrekken door onvoldoende restricties op deaccountbeheer endpoints. Ook is het mogelijk om voltooide playbook runs te wijzigen door het ontbreken van run-state validatie. Daarnaast kunnen gebruikers zonder voldoende leesrechten boards koppelen aan kanalen, waardoor lidmaatschappen van private kanalen worden blootgesteld. Channel administrators kunnen hun permissies verhogen via manipulatie van de channel member roles API. De GitLab plugin vertoont een kwetsbaarheid waardoor bots berichten met willekeurige URLs kunnen injecteren in kanalen zonder toegangsrechten. Thread membership records worden niet verwijderd bij vertrek uit een team, wat toegang tot private thread content kan geven bij herintreding. Ten slotte is er een kwetsbaarheid in de server-side validatie van BoardMember.Scheme* velden, waardoor privilege escalatie mogelijk is door het toekennen van board admin rechten aan willekeurige gebruikers, en een permissiecontrole ontbreekt bij het relinken van boards aan kanalen via de batch endpoint.
advisories.ncsc.nlAug 19, 2026extracted
Critical GitLab flaw allows attackers to modify or delete public projects (CVE-2026-19478)
Critical GitLab flaw allows attackers to modify or delete public projects (CVE-2026-19478) GitLab has released patches for two vulnerabilities, including a critical-severity code injection flaw that can be exploited without authentication. The vulnerabilities affect GitLab Community Edition (CE) and Enterprise Edition (EE) versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4. The fixes are available in GitLab 19.2.4, 19.1.6, 19.0.8, and 18.11.11. “These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately,” the company said. “GitLab.com and GitLab Dedicated are already running the patched version. GitLab.com and GitLab Dedicated customers do not need to take action,” they added. The more severe vulnerability, CVE-2026-19478 (CVSS 9.4), involves code injection through a GraphQL directive and can be exploited remotely by an unauthenticated attacker without user interaction. Successful exploitation could allow an attacker to modify or delete public projects and user data. The second vulnerability, CVE-2026-19650 (CVSS 7.1), is a cross-site request forgery issue in the GraphQL multiplex query handler. Improper request validation could allow an unauthenticated attacker to “execute mutations via GET requests,” though exploitation requires user interaction. “We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards,” the company concluded. Both vulnerabilities were reported through GitLab’s HackerOne bug bounty program.
helpnetsecurity.comAug 18, 2026extracted
GitLab Patches Critical Code Injection Vulnerability
GitLab on Monday rolled out patches for two vulnerabilities, including a critical-severity code injection flaw that can be exploited without authentication. Tracked as CVE-2026-19478 (CVSS score of 9.4), the security defect allows attackers to modify or delete user data and public projects via a GraphQL directive, GitLab explains in its advisory. The second bug is CVE-2026-19650 (CVSS score of 7.1), a cross-site request forgery (CSRF) issue impacting the GraphQL multiplex query handler. “GitLab has remediated an issue that under certain conditions could have allowed an unauthenticated user to execute mutations via GET requests due to improper request validation in GraphQL multiplex query handling,” the advisory reads. The two vulnerabilities impact all GitLab Community Edition (CE) and Enterprise Edition (EE) versions from 18.2, 19.0, 19.1, and 19.2 onwards. They were addressed in GitLab CE/EE versions 18.11.11, 19.0.8, 19.1.6, and 19.2.4. “We strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately,” GitLab notes. The patches were automatically applied to GitLab.com and GitLab Dedicated, and no action is required from their users. GitLab says both security defects were reported via its HackerOne bug bounty program. The code management and sharing platform makes no mention of any of these vulnerabilities being exploited in the wild. Related: Dozens of WebKit Vulnerabilities Patched With Fresh macOS, iOS Security Updates Related: Is Patching Dead? Vulnerability Management in the Post-Mythos Era Related: WordPress 7.0.4 Patches Remote Code Execution Vulnerability
securityweek.comAug 18, 2026extracted
Critical GitLab GraphQL Flaw Could Let Unauthenticated Attackers Delete Public Projects
GitLab has released security updates to address a critical vulnerability impacting its Community Edition (CE) and Enterprise Edition (EE) software that, under certain conditions, could allow an unauthenticated attacker to remotely modify or delete public projects and user data. The flaw, tracked as CVE-2026-19478, has been rated Critical by GitLab and assigned a CVSS score of 9.4. Released on August 17, 2026, the critical patch release arrived outside the company's usual schedule of twice-monthly updates on the second and fourth Wednesdays, five days after a routine patch release that carried no critical-rated issues. Only self-managed installations need to act. The fixes are available in GitLab 19.2.4, 19.1.6, 19.0.8, and 18.11.11. "GitLab.com and GitLab Dedicated are already running the patched version. GitLab.com and GitLab Dedicated customers do not need to take action," the company said. The following versions are affected - All versions from 18.2 before 18.11.11 19.0 before 19.0.8 19.1 before 19.1.6 19.2 before 19.2.4 The fixes do not extend to the 18.2 through 18.10 branches, which fall inside the affected range. "GitLab has remediated an issue that under certain conditions could allow an unauthenticated user to remotely modify or delete public projects and user data via a GraphQL directive," GitLab said. The CVSS vector published for the flaw indicates that it can be exploited over a network by an attacker holding no credentials, and without any action on the part of a victim. GitLab has not named the GraphQL directive involved or specified what the conditions necessary for exploitation are. The advisory discloses no exploitation of either flaw, and no public exploit code for them has surfaced on GitHub as of August 18, 2026. The second issue fixed in the release, CVE-2026-19650, has been rated High by GitLab with a CVSS score of 7.1, and concerns a cross-site request forgery (CSRF) weakness in the GraphQL multiplex query handler. Unlike the critical flaw, it requires user interaction to work. "GitLab has remediated an issue that under certain conditions could have allowed an unauthenticated user to execute mutations via GET requests due to improper request validation in GraphQL multiplex query handling," the company said. The company said the update introduces no new migrations and is not expected to require downtime on multi-node deployments. The disclosure follows a July 2026 report in which researchers published working exploit code for a separate GitLab flaw affecting self-managed servers. GitLab did not immediately respond to a request for comment. The company said it makes the issues detailing each vulnerability public on its issue tracker 90 days after the release that patched them. GitLab's June 10, 2026 patch release put that window at 30 days. That places technical details of both flaws at around mid-November 2026.
thehackernews.comAug 17, 2026extracted
Trivy, Not LiteLLM Behind the 2,500 Org Compromise
Most of the 2,500 organizations believed to have been affected by the LiteLLM supply chain attack were actually exposed before, SOCRadar reports. The compromise was blamed on and claimed by TeamPCP, the threat actor behind multiple open source software (OSS) supply chain attacks involving the Shai-Hulud worm. It started with Aqua Security’s Trivy scanner and propagated downstream to multiple packages and repositories in a ripple effect fueled by the malware’s worm-like behavior and by the automated inclusion of the malicious libraries in more builds. More than 2,500 organizations were likely affected by the LiteLLM attack, CloudSEK and HudsonRock said earlier this week. According to SOCRadar, most of them were victims of the Trivy compromise, not LiteLLM. All the compromises associated with TeamPCP followed a similar pattern: malicious code was automatically executed when the infected package was fetched and run to harvest credentials, tokens, API keys, and other secrets. Additionally, the worm used stolen developer secrets to modify accessible packages and push the malicious versions to the registry, expanding the attack surface. This is how LiteLLM was compromised and how two poisoned package versions were published on March 24 and stayed online for roughly 40 minutes. They were injected with a .pth file that Python automatically executed at interpreter startup, even if LiteLLM was never imported, bypassing ignore-scripts protections. The compromise timeframe According to SOCRadar, a close examination of the LiteLLM incident data revealed per-organization records for 2,188 entities, including timestamps, credential types, CI/CD platforms, and domains. “Every record carries first-seen and last-seen timestamps. The earliest is March 19 at 18:05 UTC and the latest is March 24 at 20:09 UTC, a span of just over five days,” the cybersecurity firm notes. For 2,085 organizations, or 95% of the 2,188 that were identified, data collection activity ended before March 24, when the poisoned LiteLLM packages were published to the registry. “That timing lines up with the upstream Trivy compromise rather than the LiteLLM install window. The 40 minutes everyone reported was the closing act, not the whole play,” SOCRadar says. The earliest collection occurred 18 minutes after the malicious Trivy build was published on March 19. The activity surged on March 22 and March 23 when malicious Trivy images were live on Docker Hub, and closed on March 24 after PyPI quarantined the packages. “[This] is what persistence on already-infected hosts looks like: the .pth payload kept running after the source of the infection was gone,” SOCRadar notes. The compromise involved six CI/CD platforms, namely GitHub Actions, GitLab CI, Jenkins, Bitbucket, CircleCI, and Buildkite, and impacted organizations worldwide, with Germany, Brazil, and France affected the most. Stolen, now brokered secrets The malware targeted secrets broadly, but over 1,000 organizations exposed JWT and auth tokens. Hundreds of them exposed private keys, AWS access keys, GitLab tokens, OpenAI API keys, Slack webhooks, GitHub Actions tokens, and Google API keys. “The highest secret count in the set is roughly 3,477 [the organization has not been named], followed by roughly 3,459. Several high-secret rows rest on very few files or repositories. One row carries 3,459 secrets across just six files,” SOCRadar notes. The cybersecurity firm also points out that committer email addresses were compromised across over 1,100 organizations. In those cases, the attackers have both developer identities and machine tokens. “Of the 2,188 organizations in the record-level set, 56% are rated high confidence, 39% medium, and 6% low, with figures rounded. Headline reporting cites 2,500+ organizations; the difference reflects which records carry attributable identifiers,” SOCRadar notes. “High-confidence matches are keyed on CI host identity and legitimate committer domains, meaning whose systems a captured file came from, rather than any observed use of a stolen credential. These are exposure figures rather than confirmed compromises, drawn from a reconstructed sample rather than a complete census,” it continues. The stolen information is already being brokered. One threat actor is offering on Telegram a collection of LiteLLM, Trivy, and CanisterWorm data, likely compiled at various stages of the campaign. Related: Over 400 NPM Packages Infected in ChainDrop Supply Chain Attack Related: North Korean Hackers Target Open Source Developers in Supply Chain Attacks Related: North Korean Hackers Blamed for Mastra NPM Supply Chain Attack Related: Hackers Exploiting Unpatched GeoServer Zero-Day
securityweek.comAug 14, 2026extracted
NCSC-2026-0297 [1.00] [M/H] Kwetsbaarheden verholpen in GitLab Enterprise Edition en Community Edition
GitLab heeft meerdere kwetsbaarheden verholpen in GitLab Enterprise Edition (EE) en Community Edition (CE) versies variërend van 12.0 tot en met 19.2.2. De kwetsbaarheden betreffen verschillende aspecten van GitLab, waaronder onjuiste privilege-toewijzing waarbij gebruikers met een pending lidmaatschapsstatus onbedoeld permissies konden erven van custom rollen. Verder zijn er problemen met ontbrekende autorisatiecontroles op API-endpoints, waardoor gebruikers met ontwikkelaarsrollen toegang konden krijgen tot externe statuscheckconfiguraties en beperkte merge request informatie van private projecten. Er is ook een Denial-of-Service mogelijk door onjuiste inputvalidatie, en cross-site scripting (XSS) kwetsbaarheden in de analytics dashboard component door onvoldoende sanitisatie van gebruikersinvoer. Daarnaast konden gebruikers met lagere rechten bepaalde package registry metadata wijzigen en CI/CD pipelines op beschermde branches triggeren zonder de juiste permissies. Er waren ook autorisatieproblemen die het mogelijk maakten om project- en groepsinstellingen ongeautoriseerd te wijzigen, en een GraphQL query die toegang gaf tot beleidsconfiguraties van niet-toegestane namespaces. Ten slotte was er een probleem met onjuiste autorisatie van identiteitinformatie, wat leidde tot verkeerde toewijzing van AI-gebruik aan andere namespaces. Deze kwetsbaarheden kunnen leiden tot ongeautoriseerde toegang, wijziging van gegevens, privilege-escalatie, en verstoring van de beschikbaarheid binnen de GitLab Enterprise Edition omgeving.
advisories.ncsc.nlAug 13, 2026extracted
153GB of stolen credentials surface after LiteLLM supply chain attack
153GB of stolen credentials surface after LiteLLM supply chain attack A massive 153GB archive stolen during the LiteLLM supply chain attack exposes credentials and other sensitive data linked to thousands of corporate domains, including AWS, Samsung, Cisco, and Salesforce. Hudson Rock says it obtained and analyzed the archive, which contains 433,909 files, and attributed 118,829 CI runner dumps to 2,488 corporate domains. “We are leveraging this data for a global ethical disclosure effort,” Alon Gal, Hudson Rock’s co-founder and CTO, told Help Net Security. “We see this as an opportunity to help organizations respond proactively before threat actors weaponize the data publicly.” LiteLLM is an open-source proxy gateway that developers use to route requests to different AI models. The LiteLLM breach had its roots in an earlier compromise of Trivy, a popular open-source vulnerability scanner. On March 19, 2026, TeamPCP, a cybercriminal group that emerged in late 2025, used stolen credentials to publish a compromised version of Trivy. LiteLLM’s build pipeline installed Trivy automatically, giving the poisoned scanner read access to the runner environment and allowing the attackers to steal the project’s PyPI publishing tokens. Using those tokens, TeamPCP published two malicious LiteLLM releases, versions 1.82.7 and 1.82.8, to the Python Package Index on March 24. “The key takeaway is how supply chains have evolved to make a single upstream breach affect thousands of companies simultaneously. A window of roughly 40 minutes in which the LiteLLM dependency was hacked led to over 430,000 instances in which millions of secrets were harvested,” Gal said. Tracing exposed secrets back to their owners The dataset contains information linked to organizations including NVIDIA, Volkswagen, Microsoft, FedEx, S&P Global, John Deere, Epic Games, Orange, TomTom, BT Group, ServiceNow, Deloitte, and Siemens. Screenshots published with the research show AWS secret access keys, Salesforce client secrets, Slack signing secrets, Azure environment variables, and AI provider API keys captured during pipeline execution. A trove of internal corporate secrets (Source: Hudson Rock) CloudSEK, working from a separate dataset built from about 434,000 stolen files, put the number of exposed organizations at close to 2,500. The company stressed that its figures reflect exposure rather than confirmed breaches. “I’ve confirmed the data is legit by the way, multiple victim orgs,” security researcher Kevin Beaumont said. “It contains a significant volume of sensitive content at orgs. It’s a massive supply chain breach due to poor AI security—not because AI is the threat, but teens can run circles around orgs obsessed with rushing out AI and poor DevOps security.” “Identifying the victims within this 153GB database presents a unique threat intelligence challenge. Accurate attribution requires looking past the surface level to analyze the actual infrastructure boundaries,” Hudson Rock noted. In one case, a leaked pipeline was tied to a committer email at SiriusXM, but infrastructure markers in the same dump, including a self-hosted GitLab instance at gitlab.adswizz.com, pointed to AdsWizz, a SiriusXM subsidiary. Hudson Rock said correct identification depends on “hard infrastructure markers rather than simple committer emails.” A large share of the dumped files have no obvious owner. According to Hudson Rock, some contain database passwords, third-party API keys, and cloud credentials without a company email address, custom domain, or internal server name that could identify the organization they came from. This means organizations may have exposed credentials in the dataset without knowing they are affected. Organizations urged to act before stolen data leaks Hudson Rock is urging organizations using AI proxy infrastructure, third-party CI/CD vulnerability scanners, or downstream AI packages to audit their environments for LiteLLM versions 1.82.7 and 1.82.8 and treat any secrets accessible to the LiteLLM environment as compromised. Organizations should also rotate cloud IAM keys and access tokens, review audit logs for anomalous activity dating back to March 24, and check for unauthorized .pth files and suspicious systemd services. “While we cannot disclose how we obtained this data, it is not leaked anywhere at the moment and is not circulating widely. This makes it a critical window of opportunity for companies to rotate keys and secrets before it eventually leaks, as is the natural cycle of a breach,” Gal added. Despite the scale of the breach, some organizations appear to be treating the exposure with less urgency than the findings warrant. “These creds date from about March. One of the orgs impacted told me they’d rotated them all and it’s a nothingburger, so I looked at their responsible disclosure policy, it allows trying creds, so I tried them all. Almost every one worked. Submitted report. One of the biggest US techcos,” Beaumont wrote. “This magnitude pushes us into a completely new world regarding the type of response required from the cybersecurity industry,” Gal concluded.
helpnetsecurity.comAug 13, 2026extracted
Chainloop: Open-source evidence store and policy engine for the software supply chain
Chainloop: Open-source evidence store and policy engine for the software supply chain Chainloop is an open source evidence store for the software supply chain. A command line tool runs inside a GitHub Actions, GitLab, Jenkins, or Dagger pipeline, picks up what the build produced, uploads those files to content-addressable storage, and references each one in a signed in-toto attestation. in-toto is a specification for recording who ran which step of a build, so the record can be checked afterward. Compliance and security teams get a control plane where all of it arrives, already signed, no matter which continuous integration provider produced it. The gap that closes is easy to see in a pipeline that lacks it. A build turns out a bill of materials listing every dependency in the release, a SARIF file recording what the static analyzer found, a coverage report, a container image reference, and a scan from whatever commercial tool the security group bought last year. Each file lands somewhere different. Nothing signed ties any of them to the commit that produced them, so when a customer asks six months later which version of a compression library shipped in a given release, someone is digging through build logs to reconstruct an answer they can’t verify. The contract does the enforcing A Workflow Contract declares what a build has to hand over: which materials, which build information, and the environment the workflow has to run in. Compliance and security teams write the contract, and Chainloop checks that the crafting of artifacts and attestation meets it, so a pipeline that stops emitting a bill of materials stops satisfying the contract. Rego policies, written in the language Open Policy Agent uses, attach to those same contracts. They are evaluated automatically and their results are written into the attestation before it is signed and stored, so the verdict on a build travels inside the signed record rather than sitting in a dashboard someone can edit later. Seventeen named evidence formats get first-class handling, and the full catalog runs longer than that. CycloneDX and SPDX bills of materials, OpenVEX, the four CSAF document types, SARIF, ZAP DAST results, BlackDuck SCA output, PrismaCloud Twistcli scans, GitLab security reports, JUnit results, JaCoCo XML coverage, Helm charts, and container image references are among them. Anything else goes in under one of four catch-all categories, as a custom evidence type, an approval report in JSON for instance, or as key-value metadata pairs. Signing is not tied to one method either: evidence can be signed through Sigstore or through an organization’s own PKI, including AWS KMS or Keyfactor, which matters to anyone whose keys have to stay in-house. Two audiences, one integration point Artifacts and evidence can be routed to an OCI registry or cloud blob storage, sent to Dependency-Track or Guac for bill-of-materials analysis, and announced in Jira, Discord, or Slack. Swapping the analysis backend requires no change to a pipeline, because the pipeline only ever talks to the crafting tool. Compliance and security teams define the contracts, craft the policies, wire up those integrations, and hold access to the control plane. Development teams get a different pitch. What the regulations require FedRamp, Executive Order 14028 in the United States, the EU Cyber Resilience Act, and the Digital Operational Resilience Act all turn questions about what shipped into questions someone has to answer on a deadline. The project publishes guides for the Cyber Resilience Act and for SLSA, the supply chain framework whose level 3 the single source of truth is built to satisfy. A FedRamp guide is listed as coming. The command line tool points at a hosted Chainloop instance by default, which is convenient for a trial and means the evidence leaves your infrastructure. Running the Helm chart on your own Kubernetes cluster puts the control plane back in-house. Chainloop is available for free on GitHub. Must read: 20 open-source cybersecurity tools to keep your team ready for anything GitHub CISO on security strategy and collaborating with the open-source community Subscribe to the Help Net Security ad-free monthly newsletter to stay informed on the essential open-source cybersecurity tools. Subscribe here!
helpnetsecurity.comAug 10, 2026extracted
TeamPCP Traced Back to 2020 Cryptojacking Operation
The group behind March's cascading supply chain attacks on open-source developer tools has been linked to infrastructure attacks dating back to 2020 and the first known self-propagating botnet built from hijacked AI infrastructure. New research published by Oligo Security on August 5 showed that TeamPCP shares domains, malware deployment paths and backend infrastructure with activity previously tracked as TA-NATALSTATUS between 2020 and August 2025. Oligo Security worked with Mandiant and GitLab on the investigation, and GitLab banned the accounts involved. The firm also assessed that TeamPCP ran ShadowRay 2.0, the campaign it documented in November 2025 against exposed Ray clusters, which it had attributed at the time to an actor called IronErn440. A Deployment Framework Reused for Years The strongest infrastructure link identified was masscan[.]cloud, which appears across TA-NATALSTATUS activity, ShadowRay 2.0 and later TeamPCP operations. Certificate transparency records date it to May 11, 2025, and TeamPCP's own GitHub account later listed it as the group's official website. Alongside it, Oligo found the same deployment framework reused for years: a distinctive directory path and a set of staging scripts documented in earlier TA-NATALSTATUS campaigns turning up unchanged in TeamPCP payloads. A compromised Ray cluster logged a download from that infrastructure on July 26, 2025, five months before the TeamPCP name surfaced publicly. The most direct evidence came from GitLab. One IP address received reverse shells from a compromised Ray cluster between October 15 and November 2. All shells terminated on November 2, and between November 2 and 4 the ironern440 account authenticated to GitLab from that same address, which hosted the campaign's tooling. From Cryptojacking to Wiper Oligo's timeline has the operators exploiting internet-facing infrastructure as early as 2020, often with automated and wormable techniques, before expanding into GitHub Actions abuse and token theft. That progression ran through PCPcat, which peaked around Christmas 2025 against React2Shell targets and exposed Docker APIs, and into the March 2026 compromises of Trivy, Checkmarx's KICS and LiteLLM. The infrastructure also broadened beyond exploitation, with subdomains observed supporting credential phishing, payment fraud and Zendesk impersonation. In late March, a second-stage Kubernetes payload gained a destructive branch. The script checked whether the victim system was set to the Iran timezone and, if so, deployed a destructive workload that deleted filesystems and rebooted the machine. Oligo noted that Iranian connectivity was heavily disrupted at the time, limiting visibility into whether it ever executed. Oligo was careful about how far the attribution extends. Whether the continuity reflects a direct rebrand, a shared operator set or close collaboration between related actors cannot be established with certainty, the firm said. What the evidence shows is that TeamPCP continues an existing operational ecosystem rather than being a new group that appeared in late 2025.
infosecurity-magazine.comAug 6, 2026extracted
Polish convenience store chain Żabka hacked through third-party account
Polish convenience store chain Żabka hacked through third-party account A cyberattack on Poland's largest convenience store chain, Żabka, has exposed internal company systems after attackers allegedly stole corporate data through a third-party contractor's account. The company confirmed on Tuesday that it detected unauthorized access to technical systems used to communicate with its franchise network late last week and immediately blocked the intrusion. According to Żabka's statement, payment systems, transaction data, the Żappka loyalty app, and day-to-day store operations were unaffected. "We assure you that the security of transaction data and consumer services, the confidentiality of Żappka app data, and our operational activities remain unaffected," the company said. It has more than 12,800 locations in Poland. The disclosure came after previously unknown hackers advertised what they claimed was stolen Żabka data for sale on a cybercrime forum for €5,000 ($5,800). According to the company, the attackers gained access by compromising an account belonging to an unspecified external service provider rather than breaching Żabka's own infrastructure directly. The retailer said that after discovering the attack, it notified Poland's data protection authority and law enforcement agencies. The company did not attribute the attack to a specific threat actor or disclose whether a ransom demand was made. Żabka did not immediately respond to a request for comment. Poland's Minister of Digital Affairs, Krzysztof Gawkowski, said on Tuesday that authorities had been informed promptly and confirmed that, based on information provided to the government, the breach did not affect customer data, payment information or retail operations. The incident became public after Polish cybersecurity outlet Niebezpiecznik reported that hackers had posted samples of the allegedly stolen data online. Based on those samples, the publication said the attackers appeared to have gained access to Żabka's Jira environment, an internal platform commonly used by companies to manage software development projects, technical support tickets and operational workflows. The hackers also claimed to possess employee and contractor information, internal documentation, passwords, authentication tokens, API keys, and source code from multiple GitLab repositories. Niebezpiecznik also reported that the attackers contacted journalists and companies working with Żabka to publicize the breach before advertising the data for sale. Those claims have not been independently verified, and Żabka has not confirmed the nature or volume of any stolen data. Daryna Antoniuk is a reporter for Recorded Future News based in Ukraine. She writes about cybersecurity startups, cyberattacks in Eastern Europe and the state of the cyberwar between Ukraine and Russia. She previously was a tech reporter for Forbes Ukraine. Her work has also been published at Sifted, The Kyiv Independent and The Kyiv Post.
therecord.mediaAug 4, 2026extracted
Microsoft shortens NuGet API key lifetime to improve supply chain security
Microsoft shortens NuGet API key lifetime to improve supply chain security Microsoft is reducing the lifetime of new NuGet.org API keys from 365 days to 30 days starting August 17, 2026, to improve the security of NuGet, its package repository for .NET developers. API keys created before August 17 will remain valid until November 1, after which developers will need to generate new keys or switch to NuGet Trusted Publishing. The change does not eliminate the risks associated with API keys, though it reduces the amount of time a stolen key can be used if exposed. Why Microsoft is making the change A NuGet.org API key functions like a password that allows developers to publish software packages. If a key is stored in a code repository, shared between systems, or included in an automated build pipeline, anyone who obtains it could publish malicious or unauthorized package updates. “Long-lived credentials are convenient, but they also significantly increase the impact of accidental disclosure. The NX Console NPM package was recently compromised using stolen credentials. The attacker published a malicious NX Console package using the stolen credentials. According to the NX Dev Team, the package was activated 6,000 times in 36 minutes before it was taken down. Other similar attacks have had a much wider blast radius,” Microsoft explained. How Trusted Publishing works Trusted Publishing, introduced in September 2025, replaces permanent API keys with OpenID Connect (OIDC) authentication. It verifies publishing requests through OIDC, issues a temporary API key for that publishing session, and automatically invalidates it afterward. The approach eliminates long-lived API keys from code repositories and CI/CD systems, verifies that publishing requests originate from approved sources, and aligns with the industry’s move toward keyless publishing. OpenID Connect (OIDC) is an identity layer built on top of OAuth 2.0. It allows an application to verify the identity of a user or service without requiring passwords to be shared with every website or service involved. What developers need to do Developers who continue using API keys should identify every workflow that publishes packages to NuGet.org and replace any keys created before August 17, 2026. Microsoft also recommends limiting each key’s permissions, avoiding storing keys in source code or logs, deleting exposed keys immediately, and ensuring expiration notices are sent to an actively monitored account. Manual package publishing through the NuGet.org website will remain available. Microsoft recommends developers using GitHub Actions or GitLab migrate to Trusted Publishing as soon as possible. Those using other CI/CD platforms should ensure their publishing workflows support API keys that expire every 30 days and replace any remaining long-lived keys before November 1, 2026. The company says it will expand Trusted Publishing support to additional CI/CD platforms over time.
helpnetsecurity.comAug 4, 2026extracted
NCSC-2026-0270 [1.00] [M/M] Kwetsbaarheden verholpen in GitLab door GitLab Inc.
GitLab Inc. heeft meerdere kwetsbaarheden verholpen in GitLab, specifiek in versies voorafgaand aan 19.0.5, 19.1.3 en 19.2.1, inclusief GitLab Enterprise Edition (EE) versies binnen deze reeksen. De kwetsbaarheden betreffen verschillende onderdelen van GitLab: Onjuiste toegangcontrole waardoor geauthenticeerde gebruikers met gastrechten testrapporten konden inzien die beperkt hadden moeten zijn. Onvoldoende validatie van gebruikersinvoer waardoor geauthenticeerde gebruikers de CI/CD pipeline schema's van andere gebruikers konden wijzigen. Onjuiste verwerking van upstream verzoeken in virtuele registries leidend tot mogelijke ongeautoriseerde informatielekken. Een raceconditie die het mogelijk maakte om de verplichte goedkeuringsworkflow te omzeilen en direct code te mergen in beschermde branches. Onvoldoende toegangscontrole bij interne verzoekverwerking waardoor ontwikkelaars toegang kregen tot informatie buiten hun autorisatie. Onvoldoende resource throttling bij het verwerken van merge request discussies, wat door niet-geauthenticeerde gebruikers misbruikt kon worden voor een denial-of-service. Onjuiste autorisatiecontroles op merge request samenwerking waardoor ontwikkelaars konden blijven committen na intrekking van hun toegang. Onjuiste autorisatie waardoor niet-geauthenticeerde gebruikers de titels van vertrouwelijke issues konden bekijken via publieke merge requests. Onjuiste verwerking van onbetrouwbare inhoud in de AI-assisted code review functie, wat toegang tot projectinformatie mogelijk maakte. Onvoldoende inputsanitatie waardoor cross-site scripting (XSS) aanvallen mogelijk waren via speciaal opgemaakte URLs. Onjuiste autorisatie tijdens token generatie waardoor geauthenticeerde gebruikers admin-governance policies konden omzeilen. Onjuiste API-toegangscontrole waardoor gebruikers met Maintainer rol beschermde branch instellingen konden wijzigen. Ontbrekende autorisatiecontrole waardoor niet-geautoriseerde gebruikers toegang kregen tot project import broninformatie. Deze kwetsbaarheden kunnen leiden tot ongeautoriseerde informatieontsluiting, manipulatie van workflows, omzeilen van beveiligingsmechanismen, denial-of-service en privilege escalatie binnen de GitLab omgeving.
advisories.ncsc.nlJul 30, 2026extracted
Researcher Publishes GitLab RCE PoC Letting Authenticated Users Run Commands as Git
Security researchers at depthfirst published working exploit code on July 24 for a GitLab flaw that GitLab patched six weeks earlier, on June 10. It runs commands as git on any self-managed 18.11.3 server that has not taken the update. Any authenticated user who can push to a project can run it. The attacker commits a crafted Jupyter notebook and opens its commit diff, which leaks a heap pointer. Enough of those and an automated probe can locate the libraries in memory. Two more notebooks then fire the payload. No administrator rights, no CI or runner access, no victim interaction, no access to anyone else's project. GitLab did not file the fix as a security fix. A review by The Hacker News found the Oj 3.17.3 bump listed under bug fixes in the June 10 patch release, not in the security-fix table. There is no CVE, no CVSS score, and no mention of the notebook-diff chain. Operators who triaged that release against the security table had no reason to treat it as urgent. Two memory corruption bugs in Oj, a Ruby JSON parser implemented largely in native C, make the chain work. depthfirst says its system flagged them autonomously, and researchers chained them by hand. GitLab's notebook renderer, an in-tree gem called ipynbdiff, passes repository-controlled .ipynb JSON to Oj::Parser.usual.parse inside a long-lived Puma worker, so attacker-controlled bytes reach Oj's manually managed C memory inside the application process. One bug writes past a fixed 1,024-byte nesting stack until it controls the parser's start callback. The other truncates a 65,565-byte object key to 29 in a signed 16-bit field and returns a live heap pointer, which GitLab renders into the diff. The leak locates libc, and the write points the callback at system(). All tiers are affected, CE and EE, Free through Ultimate. Ruby itself is not. Oj 3.17.2 carried other fixes from the same review but not these two. Upgrade to 18.10.8, 18.11.5, or 19.0.2. Neither GitLab nor depthfirst offers a workaround for anyone who cannot. depthfirst researcher Yuhang Wu told The Hacker News he is not aware of a documented GitLab option that fully disables the vulnerable notebook-diff path, and that depthfirst has not validated a configuration-only workaround it can recommend. Keeping untrusted users away from notebook-diff rendering would remove this entry point in principle, he said, but operators who cannot upgrade should ask GitLab for guidance specific to their deployment. The trap is Helm and Operator: check the GitLab version inside the Webservice image running Puma, not the chart or Operator version. Anything on 15.2 through 18.9 gets no backport, because those lines sit outside GitLab's security-maintained patch trains, so those installs have to move to a supported release instead. Commands run as git, the account behind Puma. How far that goes depends on how the install is isolated. In reach: source code, Rails secrets, service credentials, CI/CD data, and internal services the application can talk to. The public exploit is built for GitLab 18.11.3 on x86-64. Gadget offsets, register state, and jemalloc behavior all came from that image, and a recovered library base holds only until the Puma master restarts, so this is not drop-in against an arbitrary target. The Oj bugs are general, and the exploit travels further than that one image suggests. Wu said the exploitation path is not specific to 18.11.3, and that retargeting another GitLab build on the same architecture would generally need only minor adjustments, mostly updated gadget or symbol offsets. Those offsets often do not change at all across nearby releases, because the gadgets come from Ruby and system libraries rather than GitLab's own code. Architecture is the real barrier. Moving to ARM64 would mean different calling conventions, gadgets, register usage, and possibly different heap behavior, and the Ruby build, libc, allocator, and compilation environment matter more than the GitLab version does. depthfirst measured five to ten minutes for the memory search on a fresh two-worker install and projects one to two hours on longer-running ones. Its writeup has the full chain. depthfirst reported the Oj bugs on May 21, the maintainer merged fixes on May 27, and Oj 3.17.3 shipped June 4. The GitLab chain went to GitLab on June 5, was confirmed on June 8, and was patched on June 10. Wu said depthfirst did not request CVE identifiers for either issue. The GitLab chain went through GitLab's HackerOne program, which assigned depthfirst no separate identifier for it, and the two Oj bugs went straight to the maintainer with no CVE requested and none assigned to depthfirst's knowledge. The absence, he said, reflects how the disclosures were coordinated rather than anything about severity. depthfirst says it is not aware of in-the-wild exploitation, and that GitLab reproduced the RCE independently. Wu said that rests on the absence of reports and on depthfirst seeing nothing outside its own research environment, not on telemetry. The company has no access to GitLab's internal data or customer environments, he said, and GitLab is the right source for any conclusion drawn from those. Its wider Oj review produced nine more CVE advisories, none of them this chain. GitLab has not responded to questions from The Hacker News about why the fix was not classified as a security issue and whether a CVE will be assigned. This story will be updated if it does. Corrected on July 26, 2026: an earlier version said porting the exploit is real work. depthfirst says retargeting another GitLab build on the same architecture generally requires only minor offset updates; the substantial work is moving to a different architecture.
thehackernews.comJul 25, 2026extracted
Intruder brings AI-powered, on-demand penetration testing to web applications
Intruder brings AI-powered, on-demand penetration testing to web applications Intruder has announced the launch of AI Pentesting for web applications, providing on-demand penetration testing. Following its initial release of issue-level investigations last quarter, the platform now allows organizations to securely connect their codebases via GitHub or GitLab to automatically scope and launch penetration tests in minutes, with results and audit-ready reporting in hours. Mythos and Daybreak have proven that AI is extremely adept at finding security vulnerabilities. At the same time, AI is accelerating attacker capability. Annual pentests do not offer organizations the same level of protection they once did, and are misaligned to the way businesses are shipping code today. Major deployments are happening weekly, and without more frequent pentesting, security and engineering risk falling dangerously out of step. Stretched teams, faster engineering According to Intruder’s latest survey, The Security Middle Child Report, 49% of security leaders cite AI and automation as their top investment priority for 2026. Meanwhile, AI-assisted “vibe coding” is shipping insecure code faster. Engineering teams moving quickly with AI coding assistants are introducing new application vulnerabilities at pace, without sufficient security review, creating a growing need for continuous app testing. AI-enabled security solutions are now essential for security teams. Embracing autonomous capabilities is the only viable path toward a truly continuous approach to security. This shift is critical in a world where the average time-to-exploit has collapsed to a single day, a window that is projected to drop further in the coming months. “Our mission at Intruder has always been to make robust cybersecurity accessible to everyone,” said Andy Hornegold, Chief Security Technologist at Intruder. “Providing web application testing marks an exciting step on that journey. By delivering the depth of a pentest on demand and at a fraction of the price, we’re helping businesses keep up with an accelerating threat environment.” On-demand pentesting Intruder’s web application penetration testing is powered by autonomous AI agents that actively discover weaknesses across application ecosystems. Intruder’s AI Pentesting brings the strategic depth and creative problem-solving of a manual, human-led engagement into an automated framework that organizations can run on every release. Designed to transform how modern engineering and security teams manage software risk, the framework delivers critical capabilities out of the box: White-box pentests: Pentesting agents have full awareness of the system they are testing by ingesting the codebase. Built by CREST-certified pentesters: Our pentests are run by AI built and trained by CREST-certified pentesters to operate and think like the best human pentesters. Tests in minutes: Pentests run in minutes to hours, depending on the complexity of the web application being tested. No scoping or scheduling. Audit-level reporting: A full pentest report is provided that can be used as evidence for SOC 2, ISO 27001 and other compliance frameworks. Affordable accessibility: Automated web application pentest costs 25% or less than a traditional manual engagement with results available in hours instead of weeks to months. “Historically, the cost of a pentest has been very high and has taken a long time,” said Chris Wallis, CEO at Intruder. “In today’s accelerated threat environment, that timeline and cost don’t hold up. We’re ensuring that resource-constrained small and medium-sized businesses aren’t excluded from good security purely based on budget.” “Securing a global AI platform requires continuous defense,” said Zach Rattner, CTO at Yembo. “While Yembo continues to leverage human pentesters, annual assessments alone leave dangerous windows of exposure. Intruder’s AI pentesting bridges that gap by delivering human-grade depth at machine speed to keep our platform permanently hardened.”
helpnetsecurity.comJul 16, 2026extracted
Romania’s land registry hit by cyber attack, data allegedly for sale
Romania’s land registry hit by cyber attack, data allegedly for sale Romania’s National Agency for Cadastre and Land Registration (ANCPI) suffered a major disruption on Tuesday, July 14, when its e-Terra cadastre and land registry app became unavailable to users. What was first declared to be a “major technical incident” has now been confirmed as a cyber attack. While the circumstances are still being investigated by the competent state institutions, ANCPI stated that the data administered through its IT systems has not been compromised as a result of this incident. Property transactions caught in the outage “From the information we have at this time, we estimate that, most likely, the e-Terra application will not be available until the end of the current week,” the agency added in a Facebook post published on Wednesday, July 15. “We regret the situation created and assure you that our technical teams are making every effort to restore the functioning of the systems under safe conditions for all users, as soon as possible.” ANCPI promised to release updates as they continue the investigation, but in the meantime, the outage has stalled real estate transactions already in progress. Adrian Vascu, Senior Partner at Romanian business advisory firm Veridio, argued in a LinkedIn post that the disruption exposes a deeper problem: digitalized systems built without backup provisions for when they fail. “A failure can happen at any time, but it is mandatory to ensure continuity or an alternative,” he wrote. “Digitalization quickly creates dependency, but it must also ensure trust.” Threat actor claims data theft and ransomware deployment Dark Web Informer flagged that a threat actor who goes by “ByteToBreach” is trying to sell on a dark web forum data allegedly stolen from ANCPI. They claim to have compromised data of Romanian citizens and various ANCPI databases, made a copy of the agency’s GitLab servers and the source code contained within, and deployed ransomware. The threat actor provided as proof screenshots made during the intrusion. ByteToBreach is known for selling on DarkForums data stolen from a variety of organizations around the world. “Based on ByteToBreach posts, he uses a mix of multiple technical approaches: Exploiting known vulnerabilities in cloud and corporate infrastructure, reusing stolen credentials harvested from infostealers and phishing, and at times resorting to brute force or misconfiguration based access to gain footholds. Once inside, the focus is data exfiltration – employee records, databases, backups, and sensitive documents that are later sold or leaked publicly to prove claims,” says cyber threat intelligence company KELA Cyber. “Several incidents included datasets that were later corroborated by affected organizations or contained verifiable technical artifacts, underscoring that many of the actor’s claims were not mere bluff.” Given that track record, ByteToBreach’s claim may well be substantiated, but for now it remains unverified. UPDATE (July 20, 2026, 05:20 a.m. ET): “At present, ANCPI’s IT infrastructure is undergoing an extensive process of reinstallation and consolidation. The institution’s technical teams, together with cybersecurity specialists, are carrying out activities to restore, verify, and strengthen protective measures, so that services can be resumed under conditions of maximum security,” the agency stated over the weekend on its site’s homepage. ANCPI also said that the attacker did not succeed at wiping all of its backed up data, as it stores backups at several locations. “The resumption of the operation of IT applications and services will be carried out in stages, as each component is verified, secured, and validated from a cybersecurity standpoint, so that their operation takes place under conditions of maximum security and stability,” the agency added, and said that technical and criminal investigations into the attack are still ongoing. In related news, the Romanian Ministry of Investments and European Projects announced on July 16 that the Private Beneficiaries Procurement application, through which private beneficiaries of projects financed under European Union’s Cohesion Policy carry out procurement procedures, was the target of a cyber incident and is currently offline. Subscribe to our breaking news e-mail alert to never miss out on the latest breaches, vulnerabilities and cybersecurity threats. Subscribe here!
helpnetsecurity.comJul 16, 2026extracted
NCSC-2026-0222 [1.00] [M/H] Kwetsbaarheden verholpen in GitLab Enterprise Edition en Community Edition
GitLab heeft meerdere kwetsbaarheden verholpen in GitLab Enterprise Edition (EE) en Community Edition (CE) in versies variërend van 9.1 tot voor 18.11.7, 19.0 tot voor 19.0.4, en 19.1 tot voor 19.1.2. De kwetsbaarheden betreffen onder andere: Het creëren van repositories met discrepanties tussen de webinterface en de daadwerkelijke downloadbare bestanden door onjuiste verwerking van Git reference names. Onvoldoende autorisatiecontroles in GraphQL-operaties waardoor gebruikers met auditor-permissies compliance violation records kunnen aanpassen. Cross-site scripting (XSS) waarbij gebruikers met developer-permissies kwaadaardige scripts kunnen injecteren in de browser van andere gebruikers door onjuiste inputsanitatie. Ongeautoriseerde detectie van private projecten door onbevoegde gebruikers via cross-project reference pages. Bypass van autorisatiecontroles waardoor gebruikers met minimale toegangsrechten metadata van werkitems in private projecten kunnen inzien. Toegang tot opgeslagen credentials van andere gebruikers door maintainers via onvoldoende toegangsbeperkingen. Ongeautoriseerde wijziging van groepsinstellingen door foutieve autorisatiecontroles op groepsniveau. Deze kwetsbaarheden maken het mogelijk voor gebruikers met verschillende toegangsrechten om acties uit te voeren of informatie in te zien die normaal gesproken beperkt zou moeten zijn, door het omzeilen van autorisatiecontroles of het misbruiken van onjuiste inputverwerking.
advisories.ncsc.nlJul 10, 2026extracted
Microsoft patches RoguePlanet Defender zero-day vulnerability
Microsoft has released a security patch to address a Defender zero-day vulnerability known as "RoguePlanet," disclosed after the June 2026 Patch Tuesday. The flaw (tracked as CVE-2026-50656) was disclosed by a security researcher using the "Nightmare Eclipse" handle as part of an ongoing dispute with Microsoft over the company's bug bounty and vulnerability disclosure practices. They also shared a proof-of-concept exploit in a self-hosted Git repository, claiming that Microsoft had previously removed their repos hosting exploits on GitHub and GitLab. According to Nightmare Eclipse, RoguePlanet affects fully patched Windows 10 and Windows 11 devices, allowing attackers to spawn a command prompt with SYSTEM privileges via a Microsoft Defender race condition. "The exploit is a race condition, so it's a hit or miss. I have managed to get a 100% success rate on some machines while it struggled to work on others," they explained. "The PoC for RoguePlanet works regardless if real time protection is on or not," the researcher added in a follow-up update. Microsoft confirmed it was working on a patch for CVE-2026-50656 on June 16, but has yet to acknowledge that Nightmare Eclipse discovered the vulnerability. Patched via Malware Protection Engine update On Wednesday, the company addressed the RoguePlanet vulnerability by releasing Microsoft Malware Protection Engine 1.1.26060.3008, an update to the core scanning engine that powers its security solutions and services. "Microsoft has released an update to the Microsoft Malware Protection Engine that addresses the vulnerability identified by CVE-2026-50656. Please see the FAQ for more information on how to check if the new version has been installed," Microsoft noted. Over the past several months, Nightmare Eclipse has disclosed multiple other Windows zero-day exploits, including for the BlueHammer, RedSun, GreenPlasma, MiniPlasma, YellowKey, and UnDefend flaws. While some of these security vulnerabilities affect Microsoft Defender, others target BitLocker and Windows components. Microsoft fixed the GreenPlasma, MiniPlasma, and YellowKey flaws one month ago as part of the June 2026 Patch Tuesday updates. Microsoft has also reacted to Nightmare Eclipse's disclosures by issuing warnings of legal action against people engaging in what it described as "malicious activity causing real harm to our customers," leading cybersecurity experts to believe that Microsoft was directly threatening the security researcher. Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply. The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments. Get the report
bleepingcomputer.comJul 9, 2026extracted
NCSC-2026-0211 [1.00] [M/H] Kwetsbaarheden verholpen in GitLab Community Edition en Enterprise Edition
GitLab Inc. heeft meerdere kwetsbaarheden verholpen in GitLab Enterprise Edition (EE) en andere GitLab versies, specifiek in releases van versie 8.3 tot en met 19.1.1, met nadruk op versies rond 18.11.6, 19.0.3 en 19.1.1. De kwetsbaarheden betreffen verschillende onderdelen van GitLab, waaronder de package management system, DAST site profile management, CI/CD API endpoints, Snippet feature, mirror synchronisatie, en project issue tracking. Diverse problemen zijn gerelateerd aan onjuiste autorisatiecontroles, onvoldoende validatie van input en output, en onjuiste filtering van gevoelige data. Hierdoor kunnen gebruikers met beperkte of geauthenticeerde rechten onder andere: toegang krijgen tot metadata van pakketten ondanks uitgeschakelde registraties, beveiligingsregels voor pakketten omzeilen en metadata overschrijven, geheimen uit DAST site profielen uitlezen, cross-site scripting (XSS) aanvallen uitvoeren via onvoldoende padvalidatie en input sanitatie, beschermde omgevingsconfiguraties benaderen of wijzigen ondanks zichtbaarheid-instellingen, verborgen of ongeautoriseerde inhoud in Snippets plaatsen, gevoelige projectinformatie inzien zonder juiste rechten, client-side code injecteren in sessies van andere gebruikers, gevoelige informatie in logs laten verschijnen door onvoldoende filtering, vertrouwelijke issue-referenties op publieke projecten benaderen zonder authenticatie, interne netwerkresources benaderen via mirror synchronisatie door onvoldoende URL-validatie, en virtuele registry cleanup policies van andere groepen aanpassen door onvoldoende toegangscontrole. Deze kwetsbaarheden zijn aanwezig in meerdere opeenvolgende versies van GitLab en betreffen zowel authenticatie- als autorisatieproblemen, alsmede input- en outputvalidatie.
advisories.ncsc.nlJun 25, 2026extracted
GitLab Patches Code Execution, Information Disclosure Vulnerabilities
GitLab has rolled out Community Edition (CE) and Enterprise Edition (EE) security updates that resolve 13 vulnerabilities, including three high-severity bugs. The most severe is CVE-2026-10086, an XSS flaw in the Analytics dashboard of GitLab EE, rooted in the improper sanitization of user-supplied input. According to GitLab, the security defect could have allowed an authenticated user with developer rights to execute arbitrary client-side code in the context of other users’ sessions. Next in line is CVE-2026-10712, an XSS in the Web IDE workbench asset handler that could have allowed unauthenticated attackers to execute JavaScript code in users’ browser sessions. The third high-severity vulnerability is CVE-2026-12053, described as an insufficient output filtering in Duo Workflows, which could have allowed users to access sensitive information already committed to a project. The fresh GitLab CE/EE updates also resolve seven medium-severity flaws, including authorization bypass, incorrect authorization, insufficient filtering, improper input validation, and improper access control issues. Successful exploitation of these bugs could have led to settings tampering, confidential information disclosure, DAST site profile secrets exfiltration, sensitive information being written to logs, content concealment, Maven package metadata overwrite, and package metadata disclosure. Patches for all these flaws were included in GitLab CE/EE versions 19.1.1, 19.0.3, and 18.11.6. Users are advised to update their deployments as soon as possible. “These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version,” GitLab notes. Related: 25-Year-Old Vulnerability Patched in Curl Related: Chrome 149 Update Resolves 18 Severe Vulnerabilities Related: New Exploit Bypasses Apple’s Boot Defenses, Affects Millions of iPhones
securityweek.comJun 25, 2026extracted
Seemplicity AI Analysts focus remediation on exploitable risks
Seemplicity AI Analysts focus remediation on exploitable risks Seemplicity has launched AI Analysts for exposure management and response. The autonomous agents replace manual vulnerability triage by working directly within remediation workflows to conduct structured, evidence-based exploitability investigations. The old playbook is broken. AI-generated exploits have collapsed the window between disclosure and weaponization from days to hours, and the static scores and external signals teams once trusted can no longer keep pace. “The danger was never the alerts we could see, it was the handful of genuinely exploitable ones buried among them,” said Michael Varicak, manager of vulnerability management for Omnissa. “Seemplicity’s AI Analysts surface exactly that with the context to prove it, so we spend our time fixing what attackers could actually exploit.” The hard part isn’t ranking findings, it’s confirming which ones an attacker could actually reach. The Seemplicity AI Analysts answer that by investigating each asset in real time, analyzing live runtime configurations, exploit prerequisites, network reachability, code and dependency usage, and compensating controls. The result is a dramatically smaller, more actionable list of what needs immediate response, backed by transparent evidence. “Zero-day discovery at this scale pushes us out of today’s CVE disclosure process and instigates a need to reindustrialize,” said Erik Nost, senior analyst, security and risk at Forrester. “Patch Tuesday will no longer be marked on the calendar: A 30-day waiting period for patching won’t be acceptable in an environment where attackers can go from discovery to exploit in minutes.” In preliminary deployments, the Seemplicity AI Analysts found that the majority of high-severity findings were not actually exploitable, cutting alert noise and pointing teams straight at the exposures that carry real-world risk. “We’re not giving security teams another number to chase. We’re giving them the evidence to act,” said Ravid Circus, Chief Product Officer at Seemplicity. “A score can’t tell you whether a vulnerability is actually exploitable on your systems. Only context can. Our AI Analysts are unique by investigating the asset itself, the runtime conditions, the network exposure, and the code to prove what an attacker could really reach.” Seemplicity AI Analysts serve three core functions: The Host Analyst: Confirms whether a host vulnerability is truly exploitable by examining live runtime configuration, exploit prerequisites, and network reachability, then surfaces the likely owner to speed the fix. The Code Analyst: Reads source directly from GitHub, GitLab, and other connected repositories to determine whether vulnerable code is actually reachable, then hands developers a scoped, ready-to-apply fix. The SCA Analyst: Confirms which dependencies are genuinely used and reachable across the software supply chain, and powers SBOM-driven zero-day response before scanner signatures even exist. How AI Analysts work together Evidence over assumptions. Every verdict comes from a structured investigation of runtime context, threat intelligence, network exposure, and code, not a static risk score. Clear chain of reasoning. Each finding carries an auditable trail of how the verdict was reached, so security and engineering teams agree on what to fix. Built into remediation workflows. Verdicts and fixes land inside findings tables, workflow automations, and ticketing systems, with no separate validation tool or console required.
helpnetsecurity.comJun 25, 2026extracted
Claudeをかたる攻撃がアジア太平洋地域で多発 偽広告から不正コード実行へ
Trend Micro�́AGoogle�L�������p�����}���o�^�C�W���O�U���͂����B�U���҂�AI�֘A�J���c�[�����U�y�[�W�֗U����AClaude�̋��L����b�g�@�\�����p���A�F�؏��ގ�^�}���E�F�A�z�z��}���Ă���B�A�W�A�����m�n��Ŕ�Q���W�������B ���̋L������������ł��B����o�^����ƑS�Ă������������܂��B �@Trend Micro�̒�����[���ł���TrendAI Research��2026�N6��17���i���n���ԁj�AGoogle�L�������p����ClickFix�^�}���o�^�C�W���O�U���̕��͌��ʂ����\�����B�U���҂�AI�֘A�J���c�[���̗��p�҂�W�I�Ƃ��A������GitLab Pages��ɐݒu�����U�_�E�����[�h�y�[�W�֗U�����Ă����B���̌�AAnthropic��AI�T�[�r�X�uClaude�v�̋��L����b�g�@�\�����p�����@�ֈڍs�����B�����ł�7�T�Ԃɂ킽��106���̈����z�X�g����6�̔g�ɂ킽��U�����m�F�����B �@���Ђɂ��ƁA�U���҂�Google�L���𗘗p���AAI�֘A�J���c�[�����������闘�p�҂��U�y�[�W�֗U�������B�W�I�ƂȂ����u�����h�ɂ́uClaude AI�v�uChatGPT Codex�v�uPerplexity AI�v�uCursor IDE�v�uJetBrains�v�Ȃǂ��܂܂��B�����̗U���e�[�}���Ղʼn^�p���Ă����\���������ꂽ�B �@ClickFix�͗��p�Ҏ��g�ɃR�}���h���s�𑣂��\�[�V�����G���W�j�A�����O��@�Ƃ����B�U���҂͖�������i������Ƃ��APowerShell��^�[�~�i���p�R�}���h�̓\��t���Ǝ��s�𑣂��BAI�֘A�J���c�[����T���Ă���Z�p�ґw�̓R�}���h���C������Ɋ���Ă���P�[�X�������A�U�������������_�����W�I�I�肾�����Ƃ݂���B �@�U�������i�K�ł́uGitLab Pages�v���g���Ă����B�U���҂�92���̈����z�X�g�����\�z���A���K�T�[�r�X�ł���gitlab.io�z���ɋU�T�C�g��ݒu�����B�M�����̍����h���C����ʼn^�p���邱�ƂŁA���p�҂�h�䐻�i�ɂ�锻�ʂ�����ɂ����B�U�T�C�g�͒Z���Ԃő�����������A���m��Ւf�ւ̑Ή���������Ă����B �@�U���̗���́A���p�҂�AI�A�V�X�^���g�֘A������������i�K����n�܂�B�L���o�R��Claude�̃���b�g�֗U�����ꂽ���p�҂ɂ́A�uApple Support�v��uCorda Team�v�𖼏���ʂ��\�������B�����ł̓^�[�~�i�����N�����A�w��R�}���h�����s����悤�ē������B �@Trend Micro�����������Ƃ���A���ꂽ�R�}���h�͊O���T�C�g����X�N���v�g���擾�����s������e�������B�擾���ꂽ�v���O�����͂܂�macOS�����m�F���A���V�A��L�[�{�[�h����͕����̗L��������B�����ɊY�����Ȃ��ꍇ�AmacOS�f�o�C�X��W�I�Ƃ�����ގ�^�}���E�F�A��MacSync���擾���Ď��s����d�g�݂������B �@MacSync��Web�u���E�U�F�؏���Cookie�ASSH���A�Í����Y�E�H���b�g�֘A�t�@�C�������W���A�O���T�[�o�֑��M����@�\�����BTrend Micro�͋��L����b�gURL�̂������Ȃ��Ƃ�45�����m�F���Ă���A����URL�ɂ�55���̃A�N�Z�X���W�܂��Ă����B �@�n��ʂɂ݂�ƁA�A�W�A�����m�n�悩��̗U���A�N�Z�X��67.4�����߂��B��p��772���őS�̂�30.5���ɒB���A���{��201���A�V���K�|�[����188���������B�U���̑�5�g�ȍ~�̓C���h�A�t�����X�A�C�^���A�ł��A�N�Z�X�������m�F����A�L���z�M�n�悪�g�債�����Ƃ��������ꂽ�B �@Trend Micro����̘A������Anthropic�͒��������{���A�֘A�A�J�E���g�̒�~�ƈ��p���ꂽ���L����b�g�̖����������{�����B���L�`���b�g�@�\�ւ̒lj��I�ȕs�����p����������Ƃ��Ă���B �@Trend Micro�́AAI���p�g��ɔ����A�U���҂�AI�T�[�r�X�ւ̐M�������p���鎖�Ⴊ������Ǝw�E���Ă���B���Ђ͊J���҂ւ̋���A�ُ�ȃR�}���h���s�̊Ď��A���m�@�\�̓�������ƁE�@�l�ɌĂт����Ă���B�G���h���[�U�[�ɂ͍L���o�R�ł͂Ȃ������T�C�g���琻�i����肷�邱�Ƃ�A���e�����ǂ��ɂ����R�}���h�̎��s������邱�ƂȂǂ𐄏����Ă���B Copyright © ITmedia, Inc. All Rights Reserved.
itmedia.co.jpJun 21, 2026extracted
Week in review: 74k Fortinet firewall credentials stolen, Splunk Enterprise RCE under active attack
Week in review: 74k Fortinet firewall credentials stolen, Splunk Enterprise RCE under active attack Here’s an overview of some of last week’s most interesting news, articles, interviews and videos: A hardware neural network backdoor that hides in plain sight Deep learning systems on edge devices often rely on third-party-designed FPGAs and ASICs for performance and efficiency, creating supply chain risks. Researchers from the University of Tennessee and the University of Florida developed HAMLOCK, a backdoor attack that splits malicious functionality between hardware and software, making detection more difficult. Onspring CISO on where automated GRC systems fall short In this interview with Help Net Security, Nichole Windholz, CISO at Onspring, talks about the limits of automated GRC systems and continuous control monitoring. She explains why color-coded dashboards can hide nuance, how teams can check the data feeding their tools, and which risks resist measurement, such as insider behavior and vendor concentration. AI vulnerability discovery is pushing 2026 CVEs toward 66,000 Vulnerability disclosures are piling up faster in 2026 than anyone expected at the start of the year. The running count for the first few months sits well above the original projection, and the Forum of Incident Response and Security Teams (FIRST) now expects the year to land near 66,000 CVEs. Reachability makes AI threat modeling worth the trust In this interview with Help Net Security, Oscar Andersson, CTO at Oplane, explains why most scanning tools fail. They cry wolf, flagging threats that cannot run in real code. The argument centers on reachability. A finding counts only when someone walks the path to impact on a working build. The SOC’s visibility gap comes down to staffing AI has settled into security operations centers faster than any earlier wave of technology. Around four in five practitioners report reaching for AI or machine learning tools in their daily work. The catch shows up one layer down. Roughly a third of those same teams have built these tools into a defined workflow with structure, governance, and consistent validation. The rest pick up AI on their own, case by case, with no shared playbook for how it gets used or checked. The Chainguard Athena coalition already shipped 2,000 patches across 500 open source projects Chainguard launched Athena, an industry coalition that pools open source vulnerability findings and remediates them under embargo before public disclosure. The group went live with more than two dozen member organizations. Founding members include BNY, Chainguard, Cisco, Cloudflare, Corridor, DepthFirst, Docker, JPMorganChase, Kyndryl, LTIMindtree, and PwC. What happens to oversight when AI agents write a lab’s own code Inside the labs building frontier AI, a growing share of the coding gets done by the AI itself. These agents write, edit, and run software with light human oversight between steps, and they reach into production infrastructure, research pipelines, and potentially the systems that train and evaluate future models. Securing digital keys when your phone unlocks the car In this interview with Help Net Security, Alysia Johnson, President of the Car Connectivity Consortium (CCC), explains how the CCC Digital Key has grown from a single-brand feature into a standard meant to work across phones, automakers, and suppliers. Your browser tab could become encrypted storage for someone else’s files Decentralized storage networks already hand pieces of people’s data to strangers’ machines. The lasting question across these networks is whether the machine holding the data can read it. A research paper by Gregory Magarshak, a professor at IENYC, describes a system called Safecloud built on one design rule: the nodes that store data see only ciphertext, and the nodes that route data hold no keys. PhishLumos: Exposing phishing campaigns that evade detection by hiding content Phishing remains one of the most stubbornly persistent threats in cybersecurity: humans are tired, distracted, trusting, and susceptible to urgency and authority in ways that no amount of awareness training can completely overcome. The security community has largely accepted this reality and shifted focus toward automated detection systems that can intercept and block phishing threats before users see them. China-linked spies backdoored authentication stack to stay hidden for years A China-linked cyber espionage group known as Velvet Ant spent nearly a decade inside the internal network of an unnamed organization without being detected, according to the results of a forensic investigation published by cybersecurity firm Sygnia. Cisco discloses second exploited SD-WAN vulnerability in two weeks (CVE-2026-20262) Cisco has revealed another Catalyst SD-WAN Manager vulnerability (CVE-2026-20262) that its Product Security Incident Response Team observed being exploited by attackers. But the associated security advisory also states that “the vulnerability was found during internal security testing”, raising the question of how attackers came to exploit it before Cisco had disclosed it publicly. SimpleHelp RMM flaw could give attackers full access to managed endpoints (CVE-2026-48558) A critical vulnerability (CVE-2026-48558) in SimpleHelp, a popular remote monitoring and management (RMM) tool, can be exploited remotely by unauthenticated attackers to create a new “Technician” account and use it to remote into managed endpoints, execute scripts, and more. Attackers are exploiting FortiSandbox vulnerabilities Attackers have been spotted exploiting three vulnerabilities (CVE-2026-39813, CVE-2026-39808, CVE-2026-25089) in FortiSandbox, a platform that other Fortinet security products depend on for threat verdicts to enforce blocking decisions and trigger automated responses. The warning came on Monday from threat intelligence company Defused, which said that the exploit for one of the flaws is vibecoded, and likely faulty. Microsoft working on patch for RoguePlanet Defender zero-day (CVE-2026-50656) Microsoft has acknowledged the local elevation of privilege issue in Microsoft Defender that can be triggered via the “RoguePlanet” exploit, and is “working to provide a high quality security update that addresses this vulnerability.” The vulnerability, which has been assigned the CVE-2026-50656 identifier, stems from improper link resolution before file access, and can be exploited in low complexity attacks by authenticated attackers, with no user interaction required. Low-skilled attacker used Claude, Codex to breach 14 companies Researchers have long warned that AI agents could lower the skill floor for offensive cyber operations, and a recent report by OALABS (Open Analysis) researchers bears that out. After recovering and analyzing over 1,000 agent sessions from a compromised server on which an attacker deployed Anthropic’s Claude Code and OpenAI’s Codex agents, the researchers discovered how easily the attacker was able to bypass most of the agents’ guardrails, and how little he actually needed to know and do himself. 74,000 Fortinet firewall credentials exposed in FortiBleed data leak A Russian-speaking cybercriminal group has stolen credentials contained in the configuration files of nearly 74,000 Fortinet firewalls and VPN gateways around the world. The data was accidentally exposed by the group on a server, along with other artifacts and tools, and the exposure was noticed by security researcher Volodymyr “Bob” Diachenko. Law enforcement hits SocGholish: 106 servers down, 15,000 sites cleaned SocGholish, an operation that’s been delivering malware to users via fake software updates, has suffered a major blow: the international law enforcement coalition behind Operation Endgame has taken down 106 of its servers and domains, and cleaned up nearly 15,000 websites compromised to serve their malicious payloads. The result of this most recent multinational law enforcement action was announced today by the Dutch National Police and on the operation’s website. Unauthenticated RCE in Splunk Enterprise under active attack (CVE-2026-20253) CISA has added CVE-2026-20253, a critical, remotely exploitable vulnerability in Splunk Enterprise, to its Known Exploited Vulnerabilities catalog, and ordered US federal civilian agencies to apply mitigations by June 21, 2026. EU Cybersecurity Act 2.0: When good regulation goes bad Over recent years we’ve witnessed the EU becoming increasingly serious about cybersecurity. After years of watching high profile breaches, many resulting from supply chain attacks targeting our critical infrastructure, that seriousness is welcome. But good intentions and good policy are not the same thing, and the proposed EU Cybersecurity Act 2.0 is starting to look a lot more like the former than the latter. Navigating SEC, NIS2, and DORA incident disclosure timelines under pressure In this Help Net Security video, Rick Goud, Global Field CTO at Kiteworks, discusses how to handle SEC, NIS2, and DORA disclosure timelines during a security incident. Proving what a military AI model will do is the real problem Defense contractors build AI systems that task drones automatically and propose kill-chains to support soldiers. Several of these contractors have partnered with frontier AI companies to put advanced models into military tools. The systems coming out of these partnerships carry a security problem that sits outside the methods of arms control diplomacy: confirming what an AI model will do. Open-source CI/CD abuse detector guards against stolen credential attacks CI/CD Abuse Detector is an open-source project that uses a large language model to flag suspicious changes to continuous integration and continuous deployment pipelines, workflows, and automation configurations. The repository contains drop-in templates for GitHub Actions, GitLab CI, and Azure DevOps. Ukrainian national pleads guilty in connection with Conti ransomware A Ukrainian national pleaded guilty to conspiracy to commit wire fraud in connection with the deployment of Conti ransomware, which targeted more than 1,000 victims worldwide. Chinese hackers breached North American research institutions via REDCap servers A China-linked cyber espionage operation targeted North American medical research institutions through compromised REDCap servers, using custom malware to gain persistent access and collect sensitive information, Google’s Threat Intelligence Group (GTIG) researchers found. Planning a trip? Fake travel sites are multiplying this summer Cyberattacks against hospitality, travel, and recreation organizations rose 24% year over year, reaching an average of 2,291 incidents per organization each week in May 2026, according to Check Point. Crypto scammers are sending couriers to victims’ homes to collect cash Scammers behind cryptocurrency investment schemes are dispatching couriers to pick up cash from victims in person, the FBI warns. According to the agency, scammers usually approach victims through social media, text messages, or fake investment personas, luring them into cryptocurrency schemes that use fraudulent trading platforms and fabricated returns to encourage additional deposits. Cybercriminals mask malicious communications through Microsoft Teams relays The DragonForce ransomware group used a custom malware called Backdoor.Turn to hide command-and-control traffic inside Microsoft Teams relay infrastructure during an intrusion at a U.S. services company, according to Symantec. Apple is bringing Hide My Email and Sign in with Apple under one domain Apple will unify the email domains used by Sign in with Apple and iCloud+ Hide My Email under a shared domain, private.icloud.com, later this summer. Hide My Email is a service included with iCloud+, Apple’s subscription service. It allows users to generate one-time-use or reusable email addresses that forward messages to their personal inbox without revealing their actual email address. Rokarolla Android trojan targets banking and crypto users, enables device takeover A newly discovered Android banking trojan, dubbed Rokarolla, targets 217 banking and cryptocurrency applications and can execute 137 commands on infected devices, according to researchers at Zimperium. Named after its command-and-control (C2) infrastructure, Rokarolla is primarily distributed through malicious websites that impersonate popular applications such as TikTok and Google Chrome, fooling users into downloading what appears to be a legitimate app. Another healthcare firm attacked days after Novo Nordisk breach Medical technology company iRhythm Holdings disclosed a cyberattack involving certain third-party-hosted business applications that resulted in the theft of patient protected health information, proprietary data, and other personal data. The company discovered unauthorized activity on June 8, 2026, and launched an investigation with the assistance of external cybersecurity experts. AWS Continuum brings AI models to code vulnerability management AWS Continuum for code vulnerabilities, a system built to handle a vulnerability across its lifecycle, from discovery through to a fix, is now available in gated preview. It reasons over a customer’s environment, confirms which findings are real, and works toward resolution. It is model agnostic and draws on multiple frontier models, assigning each to the work where it performs best. AWS designed it to take in newer models as they become available. Malware attacks strip Roblox developers of entire games Hackers who once focused on stealing valuable Roblox items are now taking over entire games. Although Roblox operates the service, users can create and publish their own games on it. Successful games can generate substantial revenue through in-game purchases. Some developers have earned millions of dollars and built dedicated studios around their creations. Klue breach lead to Salesforce data theft, Huntress affected Cybersecurity vendor Huntress was among multiple companies hit by a breach originating at Klue, a market intelligence platform used to integrate CRM and sales data across various business tools. Senior engineers are spending their week cleaning up AI-generated code At most U.S. technology companies, machines now write the bulk of the code that ships each week. The engineer’s job has shifted toward reviewing what the AI produces, and that review gives the code high marks. Leaders rate AI-generated code as higher quality than the code their own people write, praising its clean structure, consistent style, and low count of obvious bugs at submission time. Microsoft’s workplace check-in via Wi-Fi tracks who’s in the office, and not everyone’s happy Microsoft is rolling out workplace check-in via Wi-Fi for Teams and Microsoft Places. Connect to your office network and your in-office presence updates automatically, no manual status change needed. A $2 trillion revenue shift hinges on AI data governance Across large enterprises, a single question keeps surfacing when teams want to put customer data to work. Can this record be used for a given purpose, and does the consent behind it still hold? The data sits in warehouses and customer databases, and the ability to answer that question often lags behind. That delay carries a cost. GitHub releases an open dataset for multilingual developer content Developers coordinate code across README files, issue threads, and pull request discussions. Much of that exchange happens in English, and a large share happens in other languages. GitHub has released a dataset built to help researchers and developers locate public repositories that carry non-English natural-language content. Software supply chains are heading for a transparency test Software supply chain visibility is becoming part of product security work as the EU Cyber Resilience Act (CRA) moves toward application in December 2027. ENISA’s SBOM Adoption State of Play 2026 shows organizations preparing for CRA obligations through SBOM tooling, automation, and changes to software development practices. The checklist problem behind critical infrastructure cyber safety An asset owner can meet major federal cyber compliance standards and still run equipment that lacks the engineering to withstand an attack or a failure. New research from George Mason University examines how United States cyber policy defines reasonable care for systems that control physical processes, and it finds that compliance has become a stand-in for safety. Product showcase: From phishing texts to risky Wi-Fi, Norton 360 Deluxe watches the gaps Norton 360 Deluxe combines device security, scam detection, web protection, and VPN privacy in a single subscription that covers up to five devices. It is available for Windows, macOS, Android, and iOS. Microsoft AntiSSRF open-source library helps block server-side request forgery AntiSSRF is an open-source code library from Microsoft that validates URLs and network connections to reduce server-side request forgery (SSRF) risks in web applications. It supports .NET and Node.js applications and is distributed under the MIT license. The library works as a drop-in component, giving developers a way to check untrusted input before their applications make outbound requests. Ukraine can now tap EU cyber support during major attacks Ukraine can now call on emergency cyber support from the European Union during large-scale cybersecurity incidents. The move follows a decision by the Council of the European Union to add the country to the EU Cybersecurity Reserve. What’s new in Android 17? Anti-theft tools, scam detection, and parental controls The Android 17 rollout has started for supported Pixel devices, delivering new security and privacy capabilities before expanding to other devices later this year. Most agentic AI projects in production have stalled over data problems Enterprises are connecting AI agents to live data feeds and putting them to work on tasks that once required human review, from IT operations to software development. The number doing this in production reached 32 percent in 2026, up from 29 percent the year before, according to Confluent’s annual Data Streaming Report, which surveyed 4,625 IT leaders across 14 countries. Homebrew tightens tap security, begins work on its interface Anyone who installs software through a third-party Homebrew tap runs Ruby code written by people outside the project, and that code runs without a sandbox. That risk sits at the center of Homebrew 6.0.0. It now requires a tap, along with any tap-qualified formula or cask, to be trusted before its code is evaluated or run. Google’s open standard for AI agents to discover and verify tools AI agents rely on tools, services, and other agents distributed across different teams, organizations, and platforms. Because these resources are often isolated in separate systems, agents have limited ability to discover and connect to capabilities outside their own environment. Google aims to solve this with Agentic Resource Discovery, an open specification for publishing, discovering, and verifying AI capabilities across the web, regardless of framework, protocol, or provider. GentleKiller targets more than 400 security processes across 48 products Most ransomware operations leave the work of disabling endpoint security software to their affiliates. The ransomware-as-a-service gang Gentlemen runs a different model. Its operators develop and maintain a set of tools for shutting down endpoint detection and response (EDR) products, then provide these tools directly to the affiliates who rent the gang’s encryptors. Asia-Pacific scam networks generate nearly $40 billion a year Cybercrime is taking a larger share of criminal activity in Asia and the Pacific. More than half of surveyed jurisdictions reported that cybercrime accounts for over 30% of all crimes recorded nationally, according to INTERPOL’s 2025/2026 Asia and South Pacific Cyberthreat Assessment Report. Companies are discarding the logs they need to catch a breach Many large enterprises discard most of the log data their systems generate, and they do it on purpose to keep costs down. A Dynatrace survey of 450 senior IT leaders at large enterprises found that half of organizations drop or never collect an average of 86 percent of their logs, even after filtering and aggregation. Many also limit how long they retain the logs they do keep. The rise of machine identities and agentic AI: Securing trust in the next era of digital autonomy For years, identity security has been centered on humans, ensuring that the right person has the right level of access to the right resources. But now, the same principle applies to non-human entities: machines, APIs, bots, and increasingly, AI agents. These new “digital actors” authenticate, access sensitive information, execute workflows, and even make decisions, often faster and at greater scale than any human ever could. How security teams are getting credential visibility into developer endpoints Attackers increasingly target developer machines to steal credentials. Recent supply chain attacks, including Megalodon, TrapDoor, and Miasma, focused on compromising developer environments where secrets often reside in shell histories, .env files, cloud CLI configs, local caches, and AI agent directories. To address this risk, GitGuardian has introduced Developer Endpoint Protection in ggshield, enabling organizations to discover credentials on developer workstations. Google sets timeline for Android developer verification enforcement Android’s developer verification protections will take effect on September 30, 2026, starting with users in Brazil, Indonesia, Singapore, and Thailand. Developers distributing apps through participating stores in those markets must complete the verification process by the deadline. Mastodon 4.6 adds profile Collections and two-factor controls People who run accounts on the open source social network Mastodon can now group profiles together and share those groups across the web. The 4.6 release centers on a feature called Collections, along with reworked profiles, email newsletters, server administration controls, and a set of accessibility changes. Forget traffic lights, Google’s reCAPTCHA may ask for hand gestures Google has introduced hand gesture verification for reCAPTCHA, a new method for verifying that a user is human. Google’s reCAPTCHA is part of Google Cloud Fraud Defense, a fraud and abuse prevention platform for bot, account, and transaction protection. It uses risk analysis and challenge-based verification to help organizations identify automated activity and suspicious behavior. Cybersecurity jobs available right now: June 16, 2026 We’ve scoured the market to bring you a selection of roles that span various skill levels within the cybersecurity field. Check out this weekly selection of cybersecurity jobs available right now. New infosec products of the week: June 19, 2026 Here’s a look at the most interesting products from the past week, featuring releases from ArmorCode, Barracuda Networks, Blue Planet, Flip, Fortinet, Legit Security, Tigera, and WitnessAI.
helpnetsecurity.comJun 21, 2026extracted
Loading 40 more…