From d14e82815f900834dd775dfe605d2d39bd2bb856 Mon Sep 17 00:00:00 2001 From: Bhumi Talwar Date: Tue, 14 Jul 2026 13:15:49 +0530 Subject: [PATCH] Add security tip to Ansible CVE post --- ...nsible-automation-platform-credential-leak-cve-2026-11807.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/posts/ansible-automation-platform-credential-leak-cve-2026-11807.md b/content/posts/ansible-automation-platform-credential-leak-cve-2026-11807.md index 098b5cdb0..c8c890593 100644 --- a/content/posts/ansible-automation-platform-credential-leak-cve-2026-11807.md +++ b/content/posts/ansible-automation-platform-credential-leak-cve-2026-11807.md @@ -63,3 +63,5 @@ That reframes how you should treat them: - **Watch the advisories for the tools that hold your keys,** not just the apps you write. The software most worth patching urgently is the software trusted with the most, and that is usually your automation and CI platforms, not your web app. Patch CVE-2026-11807 today if you run AAP. Then sit with the uncomfortable question it raises: if any logged-in user could have walked out with your SSH keys this week, what does that say about how much trust is concentrated in one place, and how quickly you could rotate your way out of it? + +> ***Tip:*** When working with sensitive variables in Ansible automation, always use `ansible-vault` to encrypt your variables or integrate with an external secrets manager like HashiCorp Vault. Avoid hardcoding passwords or tokens in plain text within your playbooks or inventory files, even in private repositories.