Event JSON
{
"id": "95a812dfc1429988398ee698449b601ea07f8403d0c1c0e02415f8a2cef1c43e",
"pubkey": "86b397086a130510861dd58f255fadeee1c47815185fa3bb628a06b4d6af31ac",
"created_at": 1786720356,
"kind": 1,
"tags": [
[
"proxy",
"https://infosec.exchange/@cR0w/117094505272642775",
"web"
],
[
"proxy",
"https://infosec.exchange/users/cR0w/statuses/117094505272642775",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://infosec.exchange/users/cR0w/statuses/117094505272642775",
"pink.momostr"
],
[
"-"
]
],
"content": "That word \"vault\" is doing a lot of heavy lifting there.\n\n\u003e Vault Secrets Operator 1.3.0 up to 1.4.1 is vulnerable to an arbitrary file read and credential exfiltration issue in the AppRole authentication configuration that may allow a tenant with limited Kubernetes RBAC permissions to read files from the operator pod’s filesystem and transmit their contents to a tenant-controlled endpoint, potentially leading to privilege escalation within the cluster.\n\nhttps://discuss.hashicorp.com/t/hcsec-2026-28-vault-secrets-operator-vulnerable-to-arbitrary-file-read-via-approle-secretidpath/77645",
"sig": "81c1805acb9eca0997a3f0e096951ad4f6f5c1e1b7d341e21c4c3024bb0073b37a90b10c605fa0d04e88e5b3a86680405676facea5cbf50b401dd959d8b9b8aa"
}