News for hackers. Stuff that matters.

A comment on Trigger.dev customer environment variables exposed. Parent comment

Re:Trigger.dev customer environment variables exposed by tomrod on Monday November 02, 2026 @08:59AM (#50336889)
Depends on the TOS, but, blocking service until confirmed or decommed would get the trick done.
[ Parent | on HN ]
Re:Trigger.dev customer environment variables exposed by weird-eye-issue on Monday November 02, 2026 @09:59AM (#50337712)
That doesn't even make sense. People use environment variables to store things like API keys for third-party services. How do you expect them to magically rotate or decommission those keys?
[ Parent | on HN ]
Re:Trigger.dev customer environment variables exposed by tomrod on Monday November 02, 2026 @10:40AM (#50338333)
Trigger.dev wouldn't rotate customer BYOK. What I was saying is they disable customer use of their service until rotation occurs or is confirmed by the customer.
[ Parent | on HN ]
Re:Trigger.dev customer environment variables exposed by weird-eye-issue on Monday November 02, 2026 @09:46PM (#50347366)
That doesn't really help anything and just makes the exploit impact even worse since it would be effectively a denial of service
[ Parent | on HN ]