SShortSingh.
Back to feed

Certighost CVE-2026-54121 Lets Low-Privilege Users Hijack Windows Domains via AD CS

0
·1 views

A publicly available proof-of-concept exploit for CVE-2026-54121, dubbed Certighost, allows a low-privilege domain user to fully compromise a Windows domain through Active Directory Certificate Services. The attacker creates a machine account, runs fake LDAP and LSA services, and tricks the Enterprise CA into issuing a certificate containing a real Domain Controller's SID and DNS name. Using that certificate, the attacker authenticates via PKINIT to obtain a Kerberos TGT as the DC, then performs a DCSync attack to steal domain secrets including the krbtgt hash. Microsoft's July 2026 security update addresses the flaw by requiring the CA to verify the target DC identity and enforce SID matching during certificate issuance. Organizations are advised to apply the patch promptly, restrict machine account creation, and limit CA egress traffic, as successful exploitation should be treated as a total domain compromise.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

How Laravel Developers Can Build Shared-Database Multi-Tenancy Safely

A Laravel developer has detailed the foundation layer for shared-database multi-tenancy, an architecture where all organisations share one database with rows tagged by tenant_id. The approach relies on three components: a TenantContext singleton, a BelongsToTenant trait, and composite unique constraints to enforce data boundaries. The trait automatically applies a global query scope on reads and fills tenant_id on writes, reducing the risk of one tenant accidentally accessing another's data. Unique constraints are split by purpose — human-readable identifiers are scoped per tenant, while security tokens remain globally unique to prevent collision-based attacks. A CI test that detects models missing the required trait serves as the primary guardrail, replacing reliance on developer discipline alone.

0
ProgrammingDEV Community ·

Developer applies uniform SEO checklist across five repos in a single day

A developer spent a full day applying the same SEO and analytics setup across five public repositories and several private ones built on different frameworks, including Laravel, Next.js, and Astro. Each project received meta tags, Open Graph data, canonical URLs, sitemaps, robots files, JSON-LD structured data, and environment-driven analytics. Despite differences in syntax across frameworks, the underlying concepts remained identical, making each successive project faster to configure. Notable updates included a full admin-editable SEO baseline for a Laravel starter kit, structured-data graphs for Astro sites, and per-route SEO with FAQ schema for a DevHub website. The exercise reinforced the idea that treating SEO as a portable, reusable checklist rather than a project-specific task significantly reduces time and effort.

0
ProgrammingDEV Community ·

Laravel pattern lets admins update SEO and analytics settings without redeployment

A developer building the 'Kickoff' Laravel starter kit has shared a pattern for managing SEO metadata and analytics credentials through an admin UI, eliminating the need to edit environment files or redeploy the app. The approach stores settings like Google Analytics 4 and Tag Manager IDs in a database using Spatie's laravel-settings package, then overlays them onto Laravel's config system at boot time via AppServiceProvider. This ensures all views read exclusively from config(), creating a single, consistent data path and avoiding conflicts between database and config sources. A try-catch block in the boot process allows the app to fall back gracefully to .env defaults if the settings table does not yet exist, preventing failures on fresh installs. Input validation enforces correct ID formats before saving, and conditional rendering automatically suppresses analytics snippets when no ID is configured, keeping local development traffic out of production analytics.

0
ProgrammingDEV Community ·

Developer's 30-Minute Outage Traced to a Single Overlooked Build Warning

A developer accidentally took their website offline for roughly 30 minutes while setting up a queue-based pipeline for GitHub webhooks using two Cloudflare Workers. A warning printed during deployment indicated that the second Worker's name was being overridden, causing it to be deployed as a new version of the first Worker and routed to live traffic. Because the Worker was designed to read from a queue rather than handle HTTP requests, every incoming request threw an exception until the issue was identified. The incident, which took about two hours to fully resolve, highlighted how software risks are invisible — a warning line formatted like routine output drew no attention and halted nothing. The author reflects that unlike physical hazards, risky code changes look identical to safe ones on screen, making it easy for critical warnings and edge-case risks to go unnoticed until they cause real incidents.

Certighost CVE-2026-54121 Lets Low-Privilege Users Hijack Windows Domains via AD CS · ShortSingh