Industry Category

Financial Services

Breach intelligence, attack campaigns, and threat reports targeting the Financial Services sector.

4893 threat reports
Page 16 of 408
Explore Other Sectors
AccountingAerospaceAerospace/AviationAgricultureAirlines/AviationAnimationApparel/FashionArchitecture/PlanningArtificial IntelligenceArtificial Intelligence/Machine LearningArts/CraftsAutomotiveAviation/AerospaceBanking/MortgageBiotechnology/GreentechBlockchain/CryptocurrencyBroadcast MediaBroadcasting MediaBroadcasting/MediaBuilding MaterialsBusiness Supplies/EquipmentCapital Markets/Hedge Fund/Private EquityChemicalChemicalsCivic/Social OrganizationCivil EngineeringCloud ComputingCloud Computing/SaaSCloud Native Security Fabric (CNSF)Cloud ServicesCommercial FacilitiesCommercial Real EstateComputer GamesComputer HardwareComputer NetworkingComputer Software/EngineeringComputer/Network SecurityConstructionConsultingConsumer ElectronicsConsumer GoodsConsumer ServicesCosmeticsCosmeticsCritical ManufacturingCryptocurrenciesCryptocurrencyCustomer ServicesCybersecurityDairyDating/Personal ServicesDating/Social PlatformsDefense/SpaceDesignE-LearningEducation ManagementElectrical/Electronic ManufacturingEmergency ServicesEnergyEnergy/Oil/Solar/GreentechEntertainment/Movie ProductionEnvironmental ServicesEvents ServicesExecutive OfficeFacilities ServicesFarmingFashion/ApparelFinancial ServicesFine ArtFisheryFood ProductionFood/BeveragesFortune 500 companiesFranchisingFundraisingGambling/CasinosGamingGaming/CasinosGovernment AdministrationGovernment FacilitiesGovernment RelationsGraphic Design/Web DesignHealth Care / Life SciencesHealthcareHigher Education/AcadamiaHospitalityHospitalsHuman Resources/HRImport/ExportIndividual/Family ServicesIndustrial AutomationInformation ServicesInformation Technology/ITInsuranceInternational AffairsInternational Trade/DevelopmentInternetInvestment Banking/VentureInvestment Management/Hedge Fund/Private EquityJudicialJudiciaryLaw EnforcementLaw Practice/Law FirmsLegal ServicesLegislative OfficeLeisure/TravelLogistics/ProcurementLuxury Goods/JewelryMachineryManagement ConsultingManufacturingMaritimeMarket ResearchMarketing/Advertising/SalesMechanical or Industrial EngineeringMedia ProductionMedical EquipmentMedical PracticeMilitary IndustryMining/MetalsMobileMuseums/InstitutionsMusicNewspapers/JournalismNon-Profit/VolunteeringOil/Energy/Solar/GreentechOnline PublishingOther IndustryOutsourcing/OffshoringPackage/Freight DeliveryParkingPharmaceuticalsPhilanthropyPhotographyPlasticsPolitical OrganizationPrimary/Secondary EducationProfessional ServicesProfessional TrainingPublic Relations/PRPublic SafetyPublishing IndustryRailroad ManufactureReal Estate/MortgageRecreational Facilities/ServicesReligious InstitutionsRenewables/EnvironmentResearch IndustryRestaurantsRetail IndustryRoboticsRural HealthcareSecurity/InvestigationsSemiconductorsShipbuildingSocial Media/InternetSporting GoodsSportsStaffing/RecruitingSupermarketsTechnologyTechnology/ITTelecommunicationsThink TanksToys and GamesTransportationTravel/TourismTrucking/FreightUtilitiesVenture Capital/VCWarehousingWater and Waste ManagementWater and WastewaterWater and Wastewater SystemsWater and Wastewater TreatmentWater TreatmentWater, Waste, Steam, and Air Conditioning ServicesWater/Waste ManagementWater/WastewaterWater/Wastewater ManagementWater/Wastewater/UtilitiesWholesaleWine/SpiritsWirelessWriting/Editing

Financial Services Threat Reports

Showing 181–192 / 4893 reports
eMudhra Intermediate CA Compromise: When Weak Entropy Breaks the Entire Chain of Trust
eMudhra Intermediate CA Compromise: When Weak Entropy Breaks the Entire Chain of Trust

eMudhra Intermediate CA Compromise: When Weak Entropy Breaks the Entire Chain of Trust

In October 2026, Palo Alto Networks Unit 42 disclosed that eight intermediate certificate authority (CA) private keys belonging to Indian CA eMudhra Limited were compromised due to a critical cryptographic defect introduced during certificate generation. Insufficient entropy during key generation allowed attackers to mathematically derive private keys directly from the corresponding public certificates. With access to these keys, adversaries could sign unauthorized TLS certificates, enabling meddler-in-the-middle (MitM) traffic interception, domain impersonation, and session hijacking across any domain protected by eMudhra-issued certificates. Major browser and OS vendors moved swiftly to revoke trust in the affected intermediates, and eMudhra revoked all eight certificates. This incident underscores the fragility of global PKI trust hierarchies and the cascading risk posed by a single CA's cryptographic failure. As certificate lifespans compress to 47 days and supply-chain attacks targeting cryptographic infrastructure grow more frequent, organizations must adopt automated certificate lifecycle management and continuous CT log monitoring to detect and respond to unauthorized certificate issuance before adversaries exploit it.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(high)
IImpact(high)
Read report
When the Lock Is Made of Paper: The eMudhra TLS Certificate Meltdown of 2026
When the Lock Is Made of Paper: The eMudhra TLS Certificate Meltdown of 2026
Banking/Mortgage2 weeks ago

When the Lock Is Made of Paper: The eMudhra TLS Certificate Meltdown of 2026

In October 2026, Indian Certificate Authority eMudhra Limited was found to have issued eight TLS certificates bearing catastrophically weak private keys, ranging from just 3 to 8 bits of entropy instead of the standard 384 bits required for NIST P-384 elliptic curve cryptography. The defect, likely introduced through misconfigured or example key-generation code promoted to production, rendered the certificates trivially breakable by any adversary capable of mounting a man-in-the-middle position. VPN users, non-browser TLS clients, and any relying party that trusted eMudhra's root were immediately exposed to potential traffic interception and decryption. Certificate Transparency logs surfaced the anomaly, but only after issuance, underscoring the reactive nature of current PKI oversight mechanisms. This incident arrives amid a broader wave of PKI supply-chain failures and state-sponsored traffic-interception campaigns such as Salt Typhoon, highlighting that the integrity of encrypted communications depends entirely on the rigor of every CA in the trust store. Regulators and enterprises are now under pressure to enforce continuous CT-log monitoring, automate certificate validation pipelines, and adopt network-layer encryption that does not rely solely on TLS certificate trust.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(high)
IImpact(medium)
Read report
GitLab's Max Severity RCE Flaw CVE-2026-110264: Why Your CI/CD Pipeline Is Now a Primary Attack Surface
GitLab's Max Severity RCE Flaw CVE-2026-110264: Why Your CI/CD Pipeline Is Now a Primary Attack Surface

GitLab's Max Severity RCE Flaw CVE-2026-110264: Why Your CI/CD Pipeline Is Now a Primary Attack Surface

In October 2026, GitLab disclosed CVE-2026-110264, a maximum-severity (CVSS 10.0) Remote Code Execution vulnerability rooted in an integer overflow flaw within GitLab's Regular Expression Compiler engine. An unauthenticated remote attacker could exploit this flaw by submitting a specially crafted regular expression, triggering arbitrary code execution on affected GitLab Community Edition and Enterprise Edition servers. GitLab patched the vulnerability across seven release versions and confirmed GitLab.com was already remediated. With over 2,700 internet-exposed CE instances tracked by Shadowserver and no authentication required, the attack surface is broad and the potential for supply chain compromise across GitLab's 30 million users is significant. This disclosure follows a pattern of cascading critical RCE and path traversal vulnerabilities in GitLab across 2026, one of which (CVE-2026-85706) was added to CISA's Known Exploited Vulnerabilities catalog within 24 hours of disclosure. The trend signals that DevSecOps platforms are increasingly targeted by threat actors seeking high-value footholds into software supply chains, CI/CD pipelines, and Fortune 100 development infrastructure.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
PHP2Shell: How Attackers Exploited Critical RCE Flaws Four Days Before Emergency Patches Arrived
PHP2Shell: How Attackers Exploited Critical RCE Flaws Four Days Before Emergency Patches Arrived
Internet2 weeks ago

PHP2Shell: How Attackers Exploited Critical RCE Flaws Four Days Before Emergency Patches Arrived

In October 2026, Amazon Threat Intelligence confirmed that active exploitation of two critical PHP remote code execution vulnerabilities—CVE-2026-109618 and CVE-2026-109619, collectively dubbed PHP2Shell—began four days before emergency patches were released on October 21. Attackers, operating from commercial VPN anonymization infrastructure, targeted honeypots as early as October 17, with multiple threat actors deploying proof-of-concept exploits hours after public disclosure. The PHP security team was forced to accelerate its coordinated release after CVE details and mitigation guidance leaked online two days prior. With PHP powering up to 80% of the internet, including WordPress, Drupal, and Joomla, over 3.8 million internet-exposed PHP hosts faced active risk during the zero-day window. This incident reinforces the growing reality of pre-patch exploitation windows, where threat actors acquire vulnerability intelligence through leaks or independent discovery before defenders can act. As zero-day and near-zero-day exploitation becomes standard attacker tradecraft, organizations must shift from patch-centric defense models toward runtime controls, network segmentation, and egress enforcement that limit blast radius independent of patch status.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(low)
IImpact(medium)
Read report
When 15 Seconds Is All It Takes: Machine Speed Attacks Demand Autonomous Response
When 15 Seconds Is All It Takes: Machine Speed Attacks Demand Autonomous Response

When 15 Seconds Is All It Takes: Machine Speed Attacks Demand Autonomous Response

In 2026, Exaforce documented a surge of sub-15-minute identity-driven attacks across enterprise environments. Three distinct patterns emerged: dormant OAuth tokens stolen from developer laptops via poisoned npm packages or infostealers were later weaponized to exfiltrate GitHub repositories at machine speed; ClickFix lures impersonating AI tool installers (Claude Code) deployed macOS stealers that harvested browser cookies and cloud credentials; and vishing campaigns mimicking IT help desks manipulated employees into approving real MFA prompts, granting attackers full session access within minutes. In one GitHub token case, 472 of 638 repositories were exfiltrated in under 15 seconds before containment actions could be authorized. These incidents expose a structural gap in enterprise security: detection platforms and identity providers flag anomalies but rely on human approval for response actions, leaving a critical window attackers now routinely exploit. The convergence of AI-lure social engineering, long-lived OAuth tokens, and incomplete session revocation across SaaS ecosystems signals a new normal where autonomous, low-friction response automation is no longer optional.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(high)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(high)
Read report
CVE-2026-114625: How Attackers Are Exploiting Arista VeloCloud Orchestrator to Own Your SD-WAN
CVE-2026-114625: How Attackers Are Exploiting Arista VeloCloud Orchestrator to Own Your SD-WAN

CVE-2026-114625: How Attackers Are Exploiting Arista VeloCloud Orchestrator to Own Your SD-WAN

In October 2026, Arista Networks disclosed and patched CVE-2026-114625, a critical zero-day vulnerability in VeloCloud Orchestrator (VCO) On-Prem deployments that was already being actively exploited in the wild. The flaw allows any authenticated user with basic privileges and access to the VCO web interface to escalate to operator-level privileges via low-complexity SQL injection, effectively masquerading as a local superuser. Attackers leveraging IP addresses 74.82.197.86 and 38.54.50.151 were observed exploiting the flaw, threatening the confidentiality, integrity, and availability of SD-WAN infrastructure and all data managed by the orchestrator. This is the fourth actively exploited zero-day patched by Arista in 2026 alone. This incident underscores a persistent and accelerating pattern: management-plane and orchestration-layer vulnerabilities in SD-WAN and network infrastructure are prime targets for threat actors. As enterprises consolidate network control into centralized orchestrators, a single privilege escalation flaw can hand attackers keys to the entire wide-area network, making rapid patch cadence and layered runtime controls non-negotiable.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
LiteLLM's Poisoned Pipeline: How Attackers Weaponized an AI Gateway to Steal Cloud and Developer Secrets
LiteLLM's Poisoned Pipeline: How Attackers Weaponized an AI Gateway to Steal Cloud and Developer Secrets

LiteLLM's Poisoned Pipeline: How Attackers Weaponized an AI Gateway to Steal Cloud and Developer Secrets

On October 21, 2026, attackers compromised the LiteLLM project's release pipeline and published malicious version 1.107.0 to PyPI and Docker Hub. The tampered package contained an info-stealer that harvested cloud credentials (AWS, Azure, GCP, Kubernetes), AI provider secrets, developer keys, browser data, and environment variables, encrypting the haul with AES-256-CBC under an RSA-4096 key before exfiltrating it to a threat-actor-controlled endpoint. All seven PyPI wheels and four Docker image tags were affected for roughly two hours before removal. Organizations running LiteLLM in production—including high-profile users such as NVIDIA, Netflix, AT&T, and Okta—were at risk of full secrets compromise across their AI infrastructure. This incident is the second supply-chain attack against LiteLLM within a single year, following the March 2026 TeamPCP campaign. It illustrates a rapidly maturing attacker playbook that targets AI gateway libraries to achieve broad, simultaneous credential theft across cloud, DevOps, and AI toolchains—a pattern that is accelerating as AI-integrated software becomes ubiquitous in enterprise environments.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(medium)
Read report
KSMBD Zero-Day Alert: Two Unpatched CVSS 9.0 Linux RCE Flaws Exposed on Public Mailing Lists
KSMBD Zero-Day Alert: Two Unpatched CVSS 9.0 Linux RCE Flaws Exposed on Public Mailing Lists

KSMBD Zero-Day Alert: Two Unpatched CVSS 9.0 Linux RCE Flaws Exposed on Public Mailing Lists

In October 2026, Trend Micro's Zero Day Initiative publicly disclosed two critical remote code execution vulnerabilities in the Linux kernel's KSMBD SMB server module, each rated CVSS 9.0, before any mainline kernel patch was available. ZDI-CAN-33774 requires no authentication and affects any Linux server with KSMBD active on port 445, exploiting a race condition in SMB protocol dispatch. ZDI-CAN-33549 targets SMB Direct over RDMA via an integer underflow enabling heap overflow. Neither flaw has received a CVE or upstream fix, leaving exposed systems in a prolonged window of unmitigated risk across enterprise Linux file-serving environments. The premature public disclosure—driven by a policy that AI-discovered bugs are inherently public—highlights a growing tension between responsible disclosure norms and AI-accelerated vulnerability research. With no patch and no CVE assigned, defenders have limited tooling to prioritize or track remediation, increasing the urgency for network-layer controls such as segmentation, egress filtering, and inline IPS to compensate while kernel fixes work through distribution pipelines.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
ThreatsDay October 2026: AI Secrets Leak, PingCAP Source Code Theft, Signal Hang-Up Flaw, Laravel Auth Bypass, and SafePay Ransomware's 600+ Victims
ThreatsDay October 2026: AI Secrets Leak, PingCAP Source Code Theft, Signal Hang-Up Flaw, Laravel Auth Bypass, and SafePay Ransomware's 600+ Victims

ThreatsDay October 2026: AI Secrets Leak, PingCAP Source Code Theft, Signal Hang-Up Flaw, Laravel Auth Bypass, and SafePay Ransomware's 600+ Victims

In the week of October 22, 2026, a sweeping multi-vector threat bulletin exposed simultaneous incidents across credential theft, supply-chain compromise, AI/GenAI abuse, ransomware, and critical vulnerability exploitation. PingCAP confirmed stolen service-account credentials enabled exfiltration of TiDB Cloud source code and customer records between September 9 and October 7, 2026. Zeabur announced shutdown after plaintext-credential abuse exposed 3.2 million environment variable records and 321,810 accounts. SafePay ransomware surpassed 600 victims since 2024 by chaining known edge-device CVEs with lateral movement and data exfiltration. A critical Laravel TokenGuard bypass (CVE-2026-114509, CVSS 9.2), a Signal RingRTC hang-up flaw (CVE-2026-113380, CVSS 9.3), and a NVIDIA AIStore Kubernetes host-takeover flaw (CVE-2026-65162, CVSS 10.0) compounded organizational risk across cloud, messaging, and container infrastructure. These incidents reflect a maturing attacker playbook: stolen credentials unlock supply-chain footholds, unpatched edge-device vulnerabilities feed ransomware pipelines, and AI-layer weaknesses — from biased code generation to prompt-injection via ChatGPT GitHub Connectors — are becoming primary attack surfaces. Regulatory and intelligence pressure is intensifying, with U.S. agencies banning DeepSeek from federal systems and releasing joint rogue-AI containment guidelines, signaling that AI governance is now a frontline security imperative.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(high)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(high)
Read report
eMudhra's PKI Collapse: How Trivially Weak CA Keys Triggered a 30,000-Certificate Crisis
eMudhra's PKI Collapse: How Trivially Weak CA Keys Triggered a 30,000-Certificate Crisis

eMudhra's PKI Collapse: How Trivially Weak CA Keys Triggered a 30,000-Certificate Crisis

In October 2026, Indian certificate authority eMudhra announced its exit from the global SSL/TLS certificate business after a researcher discovered that eight of its intermediate CA private keys were trivially guessable—each below the integer value 256 rather than the cryptographically large random numbers required. Disclosed on October 17, 2026 to Apple, Google, Microsoft, Mozilla, and eMudhra, the flaw prompted Chrome and Firefox to distrust the emSign ECC Root CA - G3 root within hours, affecting approximately 30,800 unexpired certificates—99.9% of them issued through InCommon, the Internet2 certificate service serving U.S. higher education institutions. eMudhra acknowledged it never used the weak keys to issue end-entity certificates, and that no systems were breached, but compounding concerns emerged around a 2025 incident in which invalid CRLs were signed with the same flawed keys, raising serious transparency questions. This incident underscores a systemic risk in the public PKI ecosystem: a single trusted CA's key-management failure can cascade to tens of thousands of relying parties overnight. With browser vendors accelerating root-store governance and higher-education institutions now scrambling to replace certificates, organizations must treat CA trustworthiness and certificate lifecycle automation as critical infrastructure concerns, not administrative afterthoughts.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(high)
Read report
Critical VeloCloud Orchestrator Zero-Day (CVE-2026-114625): Attackers Escalate to Full SD-WAN Control
Critical VeloCloud Orchestrator Zero-Day (CVE-2026-114625): Attackers Escalate to Full SD-WAN Control

Critical VeloCloud Orchestrator Zero-Day (CVE-2026-114625): Attackers Escalate to Full SD-WAN Control

In October 2026, Arista disclosed an actively exploited critical SQL injection zero-day (CVE-2026-114625, CVSS 9.9) in the VeloCloud Orchestrator (VCO), the central management plane for VeloCloud SD-WAN networks. Any authenticated user—even one holding the lowest read-only customer role—could exploit the flaw to escalate to full operator-level privileges, potentially compromising the orchestrator host, its data, and downstream VeloCloud Edge devices. Fixes were released in VCO 5.2.3.18, 6.1.3.10, and 6.4.2.12; cloud-hosted instances were patched by Arista. Two attacker-controlled IPs were observed actively exploiting the vulnerability in the wild before the patch was available. This is the third VCO zero-day exploited since July 2026, signaling a sustained, targeted campaign against SD-WAN management infrastructure. The pattern—unauthenticated flaws followed by an authenticated privilege-escalation bug—suggests attackers are systematically mapping and chaining VCO weaknesses to achieve persistent, high-privilege control over enterprise network fabrics at scale.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
PHP2Shell: How Two Critical PHP Engine Flaws Are Being Weaponized Right Now
PHP2Shell: How Two Critical PHP Engine Flaws Are Being Weaponized Right Now
Internet2 weeks ago

PHP2Shell: How Two Critical PHP Engine Flaws Are Being Weaponized Right Now

Two critical remote code execution vulnerabilities in the PHP engine, CVE-2026-109618 and CVE-2026-109619 (collectively dubbed PHP2Shell), are being actively exploited following the premature leak of technical details ahead of PHP's scheduled October 21, 2026 security release. Because the flaws reside in the PHP runtime itself rather than any single application, every web server running an unpatched PHP version is potentially exposed—spanning popular content management systems including WordPress, Drupal, and Joomla. Threat actors are leveraging public proof-of-concept code to deliver web shells, enabling persistent unauthorized access and downstream lateral movement across compromised infrastructure. PHP2Shell represents a new class of engine-level RCE risk that renders application-layer defenses insufficient on their own. With exploit code already circulating and active scanning campaigns underway, the window for undetected initial compromise is extremely narrow, reinforcing the urgency of both emergency patching and network-layer controls capable of detecting and blocking malicious payloads in transit.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(medium)
Read report
[ INCIDENT RESPONSE // UNDER ATTACK? ]

Stop Active Cloud Data Exfiltration

Aviatrix Rapid Containment helps teams instantly identify what data is leaving the environment, from which workload, and where it’s going — during an active breach.

Looking for threats in a different sector?

Browse All Threat Reports