That's exactly the threat that Monday's post about Circle CI was about! Literally 3 days to a concrete example!
The vulnerability might be the same, but the danger to users is not.
Excerpt for reference:
This is a problem because the CircleCI browser context has full access to the CircleCI API, which is hosted on the same domain, so all eight of those companies' scripts can make requests to CircleCI API endpoints. Furthermore CircleCI customers frequently either include credentials in source code or as environment variables in CircleCI. Set these, and you are trusting that CircleCI won't get compromised, or at least, your application is at most as secure as CircleCI is.