ZeroHour
DashboardNewsCVEsExploitsIncidentsAIBriefAnalyticsEntitiesWatchlistIOCsAsk the feedSourcesFeeds & APIKiosk mode
Organization

NIST

10 mentions in 7 days · 20 in 30 days · 22 total · first seen · last

Search everything

Timeline

From Protocols to Evidence: Bounded Claims for AI in Service of the Common Good

Paper proposes a rupture test and RISE AI architecture for evidence-bounded responsible-AI claims, framed via EU AI Act and NIST AI RMF.

The paper argues AI deployment intervenes in pre-existing institutional failures of responsiveness, belonging, care, and accountability, and must therefore evaluate both the system and the institutional rupture it enters. It reviews how the EU AI Act, NIST AI RMF, and ISO/IEC 42001 translate principles into protocols, and draws on Pope Leo XIV's Magnifica Humanitas to develop a rupture test linking institutional baselines to system evaluation. It distinguishes evidence-bounded deployment from measurement-bounded governance and introduces RISE AI, an architecture for bounded claims about Responsibility, Inclusivity, Safety, and Empowerment.

arXiv cs.AI / cs.LG / cs.CL · 5d agoAI policy

Best Practices for Good Endpoint Hardening | Huntress

Huntress outlines endpoint hardening best practices, citing exposed RDP, RMM tool abuse, and ClickFix social engineering as common SMB intrusion paths.

Huntress published defensive guidance on endpoint hardening for small and mid-sized businesses, drawing on observations from its SOC. The post describes common intrusion vectors: internet-exposed RDP brute-forced by automated scanners, phishing emails delivering attacker-controlled remote monitoring and management (RMM) tools, with Huntress reporting a 277% spike in RMM abuse in 2025, and ClickFix attacks using fake CAPTCHA pages that trick users into running malicious commands. Recommended controls include scanning for exposed RDP, SSH, and VPN interfaces, removing unneeded local admin rights, enabling Windows Defender tamper protection, disabling SMBv1, and standardizing on one approved remote access tool, guided by CIS and NIST frameworks.

Huntress · 5d agoAdvisory

CVE-2026-87464: RCE outside sandbox in Chromium prior to 153.0.8010.36

CVE-2026-87464 is a critical use-after-free in Chrome's WebGL allowing sandbox-escaping RCE via crafted HTML pages, fixed in 153.0.8010.36.

Google Chrome prior to 153.0.8010.36 contains a use-after-free in WebGL that allows a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. Google rates it as Chromium security severity Critical, though tracker details are restricted. Debian indicates all current Chromium packages are affected, and the flaw likely impacts Chromium-derived browsers. No active exploitation is mentioned in the disclosure.

oss-security · 5d agoVulnerabilityCVE-2026-87464

1.1.1.1 now supports post-quantum DNSSEC, all 2,420 bytes of it

Cloudflare's 1.1.1.1 resolver now validates post-quantum DNSSEC signatures using ML-DSA-44, a 2,420-byte NIST algorithm, preparing DNS for post-quantum migration by 2029.

Cloudflare enabled 1.1.1.1 to validate DNSSEC signatures using ML-DSA-44 (algorithm 18), a NIST-standardized post-quantum signature with 1,312-byte public keys and 2,420-byte signatures, roughly 38x larger than ECDSA P-256. The large signatures exceed common DNS-over-UDP limits, forcing fallback to TCP and creating downgrade risks while conventional algorithms must be published alongside. Cloudflare cites the risk of a quantum computer breaking RSA/ECDSA signatures by 2030 and plans full post-quantum security by 2029.

Cloudflare Blog · 5d agoTools1

Getting ahead of ‘harvest-now-decrypt-later’: Post-quantum cryptography planning

Opinion piece urges organizations to begin post-quantum cryptography migration now, citing harvest-now-decrypt-later risk and NIST deadlines.

CSO Online outlines why harvest-now-decrypt-later makes long-lived sensitive data a current risk even before quantum computers exist. It cites NIST IR 8547 timelines deprecating RSA-2048 and ECC P-256 by 2030 and removing them by 2035, finalized FIPS standards ML-KEM, ML-DSA, and SLH-DSA, upcoming FN-DSA (FIPS 206), NSA requirements for national security systems from 2027, and UK NCSC phased guidance through 2035. The author recommends cryptographic discovery, crypto-agility, and prioritizing long-confidentiality data and TLS endpoints.

CSO Online · 5d agoResearch

Paul Christiano joins OpenAI Foundation Board

OpenAI appointed Paul Christiano, NIST CAISI advisor and ARC founder, as non-voting observer on its Foundation Board and Safety and Security Committee.

OpenAI named Paul Christiano a non-voting observer on the OpenAI Group PBC Board and a member of the Foundation Board's Safety and Security Committee, which is chaired by Zico Kolter. Christiano is a Senior Tech Advisor at NIST's Center for AI Standards and Innovation (CAISI), where he worked on evaluating frontier AI models with national security implications, and is the founder of the Alignment Research Center (ARC). He led alignment research at OpenAI from 2017 to 2021 and contributed foundational work on reinforcement learning from human feedback (RLHF).

OpenAI Newsupdated · 6d agofirst · 6d agoAI industry 2 sources

Orchid Security targets AI agent risk with drift detection and kill switches

Orchid Security launched identity drift detection and application-level kill switches to govern AI agents that exploit enterprise identity debt.

Orchid Security announced AI readiness controls including agent discovery, continuous drift detection between an agent's intended purpose and observed behavior, and application-level kill switches that revoke credentials, disconnect tools, or suspend agent workflows. The company cites its Identity Gap 2026 finding that 57% of enterprise identity is unseen and unmanaged, which agents can leverage to gain elevated access in seconds to minutes. New integrations include a certified PAM integration for Palo Alto Networks Idira and identity telemetry streaming to Splunk Enterprise Security. The launch follows agentic enhancements to Orchid's Identity Control Plane in May 2026 and cites NIST's draft Cyber AI Profile and DORA as regulatory drivers.

Help Net Security · 6d agoAI safety & security

Dependency-Aware ROM/CBD Correctness Bounds for ML-KEM-768 at the Heuristic Failure Scale

Researchers certify a dependency-preserving upper bound of 2^-164.81 on honest decapsulation failure for ML-KEM-768 within an explicit ROM/CBD abstraction.

The paper models ML-KEM-768's domain-separated public-matrix streams as independent uniform ring elements and secret polynomials as CBD2 primitives, explicitly not claiming an information-theoretic result about the fixed SHAKE instantiation in FIPS 203. It preserves dependencies from the public matrix and both ciphertext-compression terms, using a graph-coupled reference, a proper-ideal bivariate Fourier transport, and a 256-coordinate union bound. The certified bound is Pr[K' != K] <= 2^-164.81, with the exponent 164.8107162... exceeding the 164.81 threshold by only about 0.0007162 bits; 164.82 is not certified. The bound applies to messages fixed independently of the randomness under honest encryption and decapsulation, and is not an exact DFR, a fixed-SHAKE equivalence, or a new IND-CCA reduction.

arXiv cs.CR · 6d agoResearch1

When the prompt becomes the payload: A practical pen-testing guide for GenAI, LLM and RAG applications

CSO Online publishes a practical penetration-testing guide for GenAI, LLM, and RAG applications, covering prompt injection, retrieval poisoning, and tenant isolation testing.

The guide frames LLM applications as attack graphs spanning prompts, retrieval layers, vector stores, tools, identities, and downstream APIs, arguing that conventional web testing misses instruction-vs-data channel risks. It builds on OWASP prompt injection guidance (direct vs. indirect injection) and NIST's 2025 adversarial machine-learning taxonomy, noting that RAG and fine-tuning do not remove injection risk. Recommended practices include documenting trust transitions across components, using canaries and synthetic records to avoid test side effects, running multi-turn and obfuscated injection campaigns, and verifying chains from poisoned documents to observable state changes. It also details testing RAG pipelines via controlled document poisoning across metadata, OCR layers, and code comments, plus cross-tenant isolation checks on retrieved document IDs.

CSO Online · 6d agoAI safety & security1

Lightweight Zero Trust via Automotive SDN

Researchers map automotive SDN with MACsec/MKA and CORECONF/YANG to NIST SP 800-207, satisfying five of seven Zero Trust tenets without added infrastructure.

Zonal in-vehicle networks ship Ethernet, MACsec, and TSN but treat the network itself as trusted, with no standardized runtime way to revoke access, rotate keys, or contain a compromised ECU. The paper first analyzes what Open Alliance TC17 v1.0 MACsec/MKA with pre-shared CAKs already provides against the seven NIST SP 800-207 Zero Trust tenets. It then adds CORECONF/YANG management per Open Alliance TC19, mapping the SDN Controller and Agents one-to-one onto NIST's PE, PA, and PEP, and instantiates a YANG-based network-access-control flow and key-management scheme. The result fully covers five of the seven tenets and partially covers two, without any ZTA-specific infrastructure.

arXiv cs.CR · 6d agoResearch

Why federal cyber defense demands an offense-driven mindset

Opinion piece argues federal agencies should prioritize exploitability and autonomous penetration testing over static CVSS-based patching, citing CISA's BOD 26-04 and NSA's CAPT program.

The author argues that static CVSS-driven patching leaves federal agencies exposed because vulnerable does not equal exploitable, and adversaries chain misconfigurations and stolen credentials instead of burning zero-days. The piece cites CISA's BOD 26-04 and the NSA's Continuous Autonomous Penetration Testing (CAPT) program, which logged 28,282 completed pentests across 822 Defense Industrial Base organizations and closed 71% of critical findings within 30 days. It recommends defining risk by exploitability and mission impact and augmenting human pentesting with autonomous validation and verification.

CyberScoop · 7d agoIndustry

The G7 tells industry to hurry up and prep for post-quantum encryption

A G7 working group report urges governments and industry to accelerate post-quantum cryptography migration, framing quantum risk as a near-term economic threat.

A cybersecurity working group formed at the June 2026 G7 Summit in France called on organizations to stop postponing migration of critical systems to post-quantum cryptography, warning that harvest-now-decrypt-later attacks against currently encrypted data exist today. The report was signed by CISA, the UK NCSC, France's ANSSI, Germany's BSI, Canada's CSE, Japan's NCO, and Italy's ACN. It also cautions that some NIST-selected PQC algorithms have already been broken on classical computers, reinforcing support for crypto-agility. The push aligns with a recent US executive order moving federal PQC migration timelines from 2035 to 2030, while Google and others target 2029.

CyberScoop · 12d agoPolicy & legal

Drowning in CVEs and thirsty for answers? Try CTEM

Sponsored Register piece argues traditional vulnerability management cannot scale with CVE volume and promotes Continuous Threat Exposure Management via Horizon3's NodeZero.

The sponsored article cites surging CVE volumes, CVSS triage shortcomings, NVD backlog, and AI-driven discovery accelerating an asymmetric vulnerability cycle. It outlines Gartner's five CTEM steps - scoping, discovery, prioritization, validation, and mobilization - and describes how Horizon3's NodeZero automated pentesting validates exploitable attack paths with evidence. Horizon3 says NodeZero uses a deterministic machine learning expert system rather than general LLMs, limiting generative AI to scoped tasks via AWS Bedrock.

The Register · Security · 12d agoIndustry

To keep the AI hacking genie bottled up, try one-way networks

Intuition Machines CEO proposes data diodes and one-way networks to physically prevent frontier AI models from escaping training sandboxes, citing the OpenAI Hugging Face incident.

Eli-Shaoul Khedouri, CEO of Intuition Machines, argues that sandboxes, permissions, and VMs are insufficient to contain frontier models, pointing to OpenAI's hack of Hugging Face as evidence. He proposes high assurance architectures modeled on classified SCIF environments: one-way optical data diodes for training inputs and telemetry, a sel4-verified receiver, immutable snapshots of registries like PyPI, GitHub, and npm, and mocked web services. He estimates under five percent overhead per gigawatt for such clusters, but notes frontier labs have not adopted them, largely because of competitive speed rather than cost.

The Register · Security · 12d agoAI safety & security

CMMC Hit Pause, the FAR Council Hit Play

DoD paused CMMC Phase 2 pending a 60-day review while a proposed FAR Council rule would extend NIST 800-171 Rev 3 to all federal contractors.

The Department of Defense suspended CMMC Phase 2 third-party certification requirements, but Phase 1 self-assessments under DFARS 252.204-7021 remain in force since November 2025, and prime contractors are still directing suppliers to proceed. A CMMC Reform Task Force must report recommendations to the DoD CIO within 60 days, likely by September or October 2026. Separately, the FAR Council's proposed CUI rule from June 23 would apply NIST 800-171 Revision 3, 72-hour incident reporting, and flowdown obligations to all FAR-based federal contracts, not just the defense industrial base. False Claims Act exposure grows as DIBCAC assessment teams now cooperate directly with the DOJ.

Huntress · 13d agoPolicy & legal

NIS2 compliance: Fixing IAM and access control before the 2026 audit

EU NIS2 enforcement deadlines approach; organizations are urged to prioritize service account inventory, lifecycle offboarding, and phishing-resistant MFA before audits.

EU member states are moving from NIS2 transposition into enforcement, with fines up to 10 million euros or 2% of global turnover for essential entities and personal liability for management bodies. The article argues access management is the fastest high-ROI starting point, estimating 2-4 weeks to enforce fine-grained password policy, vault shared credentials, and deploy phishing-resistant MFA versus 6-12 months for supply chain risk management. It flags three common pre-audit failures: unmanaged service accounts and API keys, dormant accounts from broken offboarding, and SMS OTP instead of phishing-resistant MFA under NIST SP 800-63B. The piece promotes Passwork as a single control plane for credential storage, RBAC, and WebAuthn.

Help Net Security · 15d agoIndustry

Three CVSS 10.0 ServiceNow Flaws Could Let Unauthenticated Attackers Execute Code and SQL

ServiceNow patched four AI Platform flaws, including three pre-authentication CVSS 10.0 issues enabling unauthenticated code execution, SQL injection, and privilege escalation.

ServiceNow released patches on August 27, 2026 for four AI Platform flaws: CVE-2026-18885 (code injection in the GraphQL Composite Data API), CVE-2026-18886 (improper access control enabling privilege escalation), and CVE-2026-74820 (SQL injection), all self-rated CVSS 10.0 and exploitable without authentication, plus CVE-2026-6876, an 8.7 sandbox escape. Updates were deployed to hosted instances, but self-hosted customers must patch affected Xanadu, Yokohama, Zurich, and Australia release lines themselves. ServiceNow says it is not aware of exploitation of the new flaws, and no public exploit code existed as of August 28, 2026; separately, Defused reported in-the-wild exploitation of the earlier CVE-2026-6875 (CVSS 9.5), later noting the captured payload matched Searchlight Cyber's PoC.

The Hacker News · 18d agoVulnerability in the wildCVE-2026-18885CVE-2026-18886CVE-2026-74820+2 CVEs

IAM Compliance Requirements and Best Practices

A guide maps IAM compliance requirements across SOX, PCI DSS, HIPAA, ISO 27001 and NIST 800-53, urging verified enforcement over documented policies.

The guide argues IAM compliance requires demonstrating that access controls are enforced at runtime, not merely documented, highlighting gaps between policy intent and application-layer execution. It maps recurring requirements across SOX ITGCs, PCI DSS v4.0, HIPAA, ISO/IEC 27001:2022, NIST SP 800-53 and GDPR, covering least privilege, separation of duties, access certification and audit trails. It recommends continuous, evidence-backed verification and application-layer telemetry instead of relying on identity provider logs or quarterly access reviews.

The Hacker News · 18d agoIndustry

NIST Warns of Unique Security Risks in Multi-Cloud Environments

NIST catalogued 23 novel security challenges unique to multi-cloud environments and urged the community to develop solutions.

NIST published an analysis identifying 23 distinct security challenges that arise specifically in multi-cloud environments. The agency explicitly encouraged the cybersecurity community to work on solutions for these gaps. The publication reflects growing official concern that spanning multiple cloud providers creates risk patterns not covered by single-cloud security models.

Infosecurity Magazine · 22d agoAdvisory

$20 per zero-day is already the WordPress plugin reality

TrendAI and CHT Security used an AI pipeline to find over 300 verified WordPress plugin zero-days at roughly $20 per vulnerability.

A pipeline built in three days by TrendAI and CHT Security, presented at Ekoparty Miami, paired AI-driven static analysis with automated Docker provisioning and Chrome DevTools MCP dynamic verification to surface more than 300 critical zero-days in WordPress plugins within 72 hours. The run consumed about 222 million tokens across 95 tasks, averaging roughly $20 per verified vulnerability, with findings including pre-auth RCE, SQL injection, privilege escalation, SSRF, and an AI-assembled downgrade attack chain. Dynamic verification eliminated over 80% of false positives, but manual review at 30-60 minutes per finding remains the bottleneck, straining ZDI and NIST triage backlogs.

Help Net Security · 22d agoResearch1

NIST Seeks Public Input on AI-Ready NVD Modernization

NIST is seeking public comment on modernizing the National Vulnerability Database to support AI-powered vulnerability research.

The US National Institute of Standards and Technology announced it is soliciting public input on modernizing the National Vulnerability Database. The initiative aims to make the NVD AI-ready to support AI-powered vulnerability research and analysis.

Infosecurity Magazine · Aug 12, 2026Policy & legal

NIST wants to overhaul its vulnerability database for the AI age

NIST issued a Federal Register RFI seeking public input on overhauling the National Vulnerability Database for AI-scale, machine-consumable security data.

NIST published a request for information arguing the National Vulnerability Database must adapt as LLMs increasingly find and exploit vulnerabilities at machine scale. The RFI seeks input on integrating automation into vulnerability reporting, faster dissemination to defenders, and transparency and auditability in AI-driven decisions. It follows the White House-backed Gold Eagle clearinghouse at Treasury and the VINCE program with Carnegie Mellon's Software Engineering Institute for AI-discovered vulnerability reports.

CyberScoop · Aug 11, 2026Policy & legal

Related CVEs

  • CVE-2026-1888610.0<1%
    Improper Access Control (Privilege Escalation) in ServiceNow AI Platform
    CVE-2026-18886 is an improper access control vulnerability (CWE-284) in the ServiceNow AI Platform that, in certain circumstances, allows an unauthenticated remote user to create or modify instance data beyond what was intended. Because the flaw is reachable over the network with no privileges or user interaction required, an attacker who meets the advisory's conditions can manipulate instance data and achieve privilege escalation. Successful exploitation carries high impact to the confidentiality, integrity, and availability of the affected instance (CVSS 4.0 score of 10.0). Customers running affected ServiceNow AI Platform releases are potentially affected; ServiceNow has already deployed the security update to hosted instances, while self-hosted customers and partners must apply the provided update themselves. No exploitation has been observed to date (EPSS 0.2%, not listed in CISA KEV, no public proof-of-concept).
    · ServiceNow AI Platformlarge
  • CVE-2026-7482010.0<1%
    Unauthenticated SQL Injection in ServiceNow AI Platform
    CVE-2026-74820 is a critical (CVSS 4.0: 10.0) SQL injection flaw (CWE-89) in the ServiceNow AI platform that an unauthenticated attacker can, in certain circumstances, trigger remotely over the network. Successful exploitation allows arbitrary SQL statements to be executed against the instance's underlying database, giving the attacker access to or the ability to modify instance data beyond what was intended, with the CVSS scoring indicating high impact to confidentiality, integrity, and availability. Any organization running an unpatched ServiceNow instance is affected, but ServiceNow has already deployed the security update to its hosted instances, so remaining exposure is concentrated among self-hosted customers and partners who must apply the provided update themselves. There is currently no known malicious exploitation: EPSS assigns a 0.2% probability of exploitation within 30 days, the flaw is not in CISA KEV, and no public proof-of-concept is known.
    · ServiceNow AI platformmass
  • CVE-2026-687610.0<1%
    Unauthenticated Sandbox Escape Allows Code Execution in ServiceNow AI Platform
    CVE-2026-6876 is a sandbox escape in the ServiceNow AI Platform (CWE-94, CWE-693, CWE-1284) that allows an unauthenticated, network-based attacker to execute arbitrary code within the platform. Triggering requires no privileges and no user interaction, consistent with the CVSS 4.0 base of 10.0 (AV:N/PR:N/UI:N with high impact across confidentiality, integrity, and availability). Successful exploitation grants arbitrary code execution inside the platform and potentially more access to the ServiceNow AI Platform than intended. All deployments of the ServiceNow AI Platform are affected: ServiceNow has already deployed the remediation to its hosted (SaaS) instances and has provided the update to partners and self-hosted customers. ServiceNow is not currently aware of malicious exploitation, and no public proof-of-concept is known.
    · ServiceNow AI Platformlarge
  • CVE-2026-1888510.0<1%
    Unauthenticated Code Injection in ServiceNow AI Platform (CVSS 10.0)
    ServiceNow has remediated an unauthenticated code injection vulnerability (CWE-94) in the ServiceNow AI platform, scored a maximum 10.0 in CVSS 4.0, exploitable over the network with no privileges and no user interaction. An attacker can trigger it, in certain circumstances, via crafted input to an affected instance, gaining the ability to execute arbitrary code on the platform and access or modify instance data beyond intended permission boundaries. All customers running the affected platform are in scope: ServiceNow has already deployed the fix to hosted instances, while partners and self-hosted customers must apply the provided update or upgrade to a patched release. Related reporting indicates this is one of three CVSS 10.0 ServiceNow flaws disclosed together that could allow unauthenticated code and SQL execution, though specific affected version ranges are not listed in the advisory. There is no public proof-of-concept, the flaw is not in CISA's KEV, EPSS is low (0.4% in 30 days), and ServiceNow states it is not currently aware of malicious exploitation.
    · ServiceNow AI platformmass
  • CVE-2026-874649.6<1%
    Use-After-Free in WebGL in Google Chrome Allows Code Execution Outside the Sandbox
    CVE-2026-87464 is a use-after-free (CWE-416) in the WebGL component of Google Chrome affecting versions prior to 153.0.8010.36. A remote attacker can trigger it by luring a user to open a crafted HTML page, which corrupts memory in the browser's WebGL rendering path. Successful exploitation allows arbitrary code execution outside the browser sandbox, meaning the attacker escapes Chrome's process isolation and runs code with the privileges of the browser on the host. All Chrome users running an unpatched version before 153.0.8010.36 are affected. As of now there is no public proof-of-concept and this specific flaw is not in CISA KEV, although the Chrome 153 release headlines reference a separate V8 zero-day that was exploited in the wild.
    · google chrome all versions prior to 153.0.8010.36mass
  • CVE-2026-68759.578%
    Unauthenticated Remote Code Execution in ServiceNow AI Platform
    ServiceNow has patched a critical, unauthenticated remote code execution vulnerability (CWE-94, code injection) in the ServiceNow AI platform that is reachable over the network without credentials or user interaction, though exploitation requires certain circumstances to be met (CVSS 4.0 attack complexity is high). A remote attacker who successfully triggers the flaw can execute code within the ServiceNow platform, with potentially high impact on the confidentiality, integrity, and availability of the instance and its data. Both ServiceNow-hosted (SaaS) instances and self-hosted customer and partner deployments are affected; hosted instances were fixed via a centrally deployed security update, while self-hosted customers and partners must apply the provided security updates or patched family releases themselves. ServiceNow's advisory states it was not initially aware of exploitation, but subsequent security reporting indicates this pre-auth RCE has been exploited in the wild. There is no known public proof-of-concept and the flaw is not yet in CISA's KEV catalog, but EPSS assigns a 77.6% probability of exploitation within 30 days.
    · ServiceNow AI Platform (hosted/SaaS instances) · ServiceNow AI Platform (self-hosted customer and partner deployments)mass

Appears with

vendor NIST 3organization NSA 3organization CISA 3vendor Microsoft 2product National Vulnerability Database 2organization ISO 2organization NCSC 2organization Center for AI Standards and Innovation 1organization Carnegie Mellon Software Engineering Institute 1organization Alignment Research Center 1organization CSE 1organization Debian 1organization Defused 1organization Department of Defense 1organization Cloud Security Alliance 1organization BSI 1
Entities are extracted by the model from each article. Watching an entity keeps it in this browser only (no account); the watchlist page and dashboard alerts use it.