<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Privilege-Escalation on it-learn.io | IT, Networking &amp; Cybersecurity Blog</title><link>https://blog.it-learn.io/tags/privilege-escalation/</link><description>Recent content in Privilege-Escalation on it-learn.io | IT, Networking &amp; Cybersecurity Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 20 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.it-learn.io/tags/privilege-escalation/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes RBAC Bypass: When Least Privilege Isn't Actually Configured</title><link>https://blog.it-learn.io/posts/2026-04-20-kubernetes-rbac-misconfiguration-privilege-escalation/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.it-learn.io/posts/2026-04-20-kubernetes-rbac-misconfiguration-privilege-escalation/</guid><description>&lt;p&gt;Kubernetes RBAC (Role-Based Access Control) is the cluster&amp;rsquo;s primary authorization system. Properly configured, it enforces least privilege so that a compromised pod, developer account, or CI/CD pipeline cannot escalate to cluster control. In practice, RBAC is frequently misconfigured in ways that create exactly the escalation paths it was designed to prevent.&lt;/p&gt;
&lt;p&gt;The misconfigurations are often subtle: a wildcard that looks like a shortcut, a &lt;code&gt;cluster-admin&lt;/code&gt; binding on a CI service account for convenience, a default service account left with auto-mounted tokens. This post maps the complete attack surface, demonstrates exploitation techniques, and provides the audit commands and policies to detect and remediate each issue.&lt;/p&gt;</description></item><item><title>Container Escape: Breaking Out of Docker Into the Host</title><link>https://blog.it-learn.io/posts/2026-04-19-container-escape-breaking-out-of-docker/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.it-learn.io/posts/2026-04-19-container-escape-breaking-out-of-docker/</guid><description>&lt;p&gt;Containers are not virtual machines. This is one of the most consequential misunderstandings in modern infrastructure security. Where a virtual machine has a full hypervisor isolation layer separating guest and host kernels, a container shares the host kernel directly. The isolation that makes containers lightweight — Linux namespaces and cgroups — is also what makes them escapable when misconfigured or when vulnerabilities are present.&lt;/p&gt;
&lt;p&gt;This post examines how container isolation works at the kernel level, walks through the primary escape vectors with working demonstrations, covers real CVEs that enabled escapes, and provides a concrete detection and hardening framework.&lt;/p&gt;</description></item></channel></rss>