ZeroHour
DashboardNewsCVEsExploitsIncidentsAIBriefAnalyticsEntitiesWatchlistIOCsAsk the feedSourcesFeeds & APIKiosk mode

Search: “lifecycle”

7 stories in the last 24h

Searchkeywordsmart Sortlatesthotimportancerelevance
DomainAllCyberAIWindow24h3d7d30dAllIn the wildImportant onlyShow duplicates
CategoryAllAdvisory 2Industry 2Malware 2Vulnerability 2
SeverityAllcritical 0high 2medium 3low 0info 3

Enterprise Threat Intelligence Buying Guide: How to Choose the Right Solution

ANY.RUN published a buyer's guide for enterprise threat intelligence platforms, outlining evaluation criteria and promoting its own TI products.

ANY.RUN, whose sandbox, TI Lookup, and TI Feeds products are featured throughout, published guidance for selecting an enterprise threat intelligence provider. The guide recommends defining SOC or MSSP requirements first, then weighing intelligence quality and freshness, integrations including STIX/TAXII support, privacy, scalability, and proof-of-concept testing with real alerts. It emphasizes context and enrichment over raw data volume, citing figures such as TI Lookup results in about 2 seconds and 99% validated IOCs in its feeds.

ANY.RUNupdated · 4h agofirst · 4h agoIndustry 3 sources

AI agent authorization risks remain a gap in new NIST-CISA token security guidance

NIST and CISA release IR 8587 guidance on securing signed tokens, but AI agent authorization and delegation risks remain out of scope.

NIST, with CISA support, published 'Protecting Tokens and Assertions from Forgery, Theft, and Misuse' (NIST IR 8587), recommending continuous monitoring and tighter token lifecycle controls for SSO and API access. The guidance does not yet fully address AI agent identity, delegation chains, or prompt injection steering agents with valid tokens, and NIST says new or expanded standards are needed. Experts recommend treating AI agents as low-trust non-human identities, maintaining agent inventories, expiring credentials after task completion, and requiring human approval for high-risk actions. The report references shared-signal mechanisms like CAEP and RISC, and follows a May incident where a CISA contractor GitHub repository exposed AWS and GitHub tokens.

CSO Online · 20h agoAdvisory 3 sources

The skb that wasn't freed - the Fragnesia primitive via Open vSwitch

Doyensec details CVE-2026-90049 in Open vSwitch, enabling deterministic Linux kernel local privilege escalation on default major distribution installs.

Doyensec reports that the Open vSwitch datapath strips the SKBFL_SHARED_FRAG flag from packets it is still forwarding, allowing an in-place decrypt to write attacker-chosen bytes into root-owned page cache — a Dirty COW-class primitive that re-opens the Fragnesia bug family. The issues are tracked as CVE-2026-90049, CVE-2026-89487, and CVE-2026-80977, and were reported to the kernel security team with fixes coordinated alongside OVS maintainers. A deterministic local privilege escalation works on default installs of Arch, Fedora, Debian, Amazon Linux, and RHEL where unprivileged user namespaces and openvswitch auto-loading are enabled; the fix landed in mainline and shipped in stable on 09/04/2026. The write technique builds on the earlier Fragnesia and Dirty Frag bugs, including CVE-2026-43284 and CVE-2026-43500.

Lobsters · security · 4h agoVulnerabilityCVE-2026-90049CVE-2026-89487CVE-2026-80977+2 CVEs

12 Serverless Security Options Compared (2026): Features & Pricing

A buyer-focused comparison of twelve serverless security offerings concludes no standalone SKU is worth buying in 2026, with function protection bundled inside CNAPP contracts.

The scorecard compares twelve serverless security options on function-protection depth, pricing visibility, platform attach economics, multi-runtime coverage, and vendor viability. Microsoft Defender for Cloud tops the weighted scores at 4.75, with Prisma Cloud at 4.60 and Datadog at 4.55 noted for publishing clean per-function rates. The piece warns that Thundra and Epsagon are defunct and that most vendors bill functions inside platform units where costs are hard to see. It also references the Aqua Security Trivy supply chain incident and Google's finalized acquisition of Wiz as market context.

GBHackers · 4h agoIndustry 12 sources

RatHat Abuses Android Wireless Debugging to Gain Shell Access and Steal Banking PINs

New Android banking trojan RatHat abuses Wireless Debugging to gain shell access and steals banking PINs and OTPs via raw touch capture.

Zimperium and zLabs analyzed RatHat, an Android banking malware linked to China-based actors that chains Accessibility abuse and Wireless Debugging to obtain a local ADB shell without a host computer. Masqueraded Go binaries in /data/local/tmp provide persistence and an FRP reverse tunnel, while a getevent-based collector maps touch coordinates to PIN pads and pattern locks using locateValues.json layouts. It targets banking, crypto, WeChat and Alipay apps through smishing, malicious ads, and HTML overlays, and serializes the accessibility tree for a generative AI assistant to automate on-screen actions. Layered anti-analysis includes malformed DEX, a padded manifest, and debugger, Frida, and emulator checks.

GBHackersupdated · 3h agofirst · 4h agoMalware in the wild 2 sources

Oracle Corporation security advisory (AV26-929)

CCCS relays Oracle's September 2026 Critical Patch Update fixing vulnerabilities across WebLogic, Database, E-Business Suite, PeopleSoft, Siebel, and dozens more products.

The Canadian Centre for Cyber Security (AV26-929) relays Oracle's September 2026 Critical Security Patch Update, which addresses vulnerabilities in dozens of product families as of September 15, 2026. Affected products include Oracle WebLogic Server, Database Server, E-Business Suite, Fusion Middleware, PeopleSoft Enterprise, Siebel Applications, GraalVM, VirtualBox, Coherence, and numerous banking and communications suites. The bulletin lists no CVE identifiers and encourages administrators to review Oracle's advisory and apply patches.

Canadian Centre for Cyber Security · 17h agoAdvisory 3 sources

VU#369093: MLflow dspy and statsmodels flavors bypass pickle deserialization control

CERT/CC warns MLflow's dspy and statsmodels flavors bypass the MLFLOW_ALLOW_PICKLE_DESERIALIZATION control, enabling remote code execution.

CERT/CC vulnerability note VU#369093 describes a flaw in MLflow 3.12.0 where the dspy flavor conditionally applies the pickle deserialization safety control based only on the model path's .pkl extension, while the statsmodels flavor skips the check entirely, permitting arbitrary code execution via malicious pickle payloads even when users disallow pickle. The statsmodels flavor is patched in versions 3.15.0 and later, but no dspy fix exists yet, so users should avoid loading models through that flavor. Exploitation requires write access to any location from which a user obtains MLflow models.

CERT/CC Vulnerability Notes · 19h agoVulnerability