feat: update advisories (#141)

🤖 beep boop - looks like there's some changes to the advisories!

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

Author: Ackama-Security-Auditor

advisories/simple_oauth/DSA-CONTRIB-2025-114.json

@@ -1,12 +1,12 @@
 {
   "schema_version": "1.7.0",
   "id": "DSA-CONTRIB-2025-114",
-  "modified": "2025-10-29T17:53:22.000Z",
+  "modified": "2025-10-29T20:15:52.000Z",
   "published": "2025-10-29T16:44:39.000Z",
   "aliases": [
     "CVE-2025-12466"
   ],
-  "details": "This module introduces an OAuth 2.0 authorization server, which can be configured to protect your Drupal instance with access tokens, or allow clients to request new access tokens and refresh them.\n\nThe module doesn't sufficiently respect granted scopes, it affects all access checks that are based on roles. For example: routes that have the `_role` requirement, can be bypassed with an access token.\n\nThis vulnerability is mitigated by the fact that an attacker must have the access token in possession and the user related to the token must have the associated (role requirement) roles assigned.",
+  "details": "This module introduces an OAuth 2.0 authorization server, which can be configured to protect your Drupal instance with access tokens, or allow clients to request new access tokens and refresh them.\n\nThe module doesn't sufficiently respect granted scopes, it affects all access checks that are based on roles. For example: routes that have the `_role` requirement, can be bypassed with an access token.\n\nThis vulnerability is mitigated by the fact that an attacker must have the access token in possession and the user related to the token must have the associated (role requirement) roles assigned.\n\n*Update: the Affected versions field was updated to reflect that this vulnerability was present in the 6.0.0 release and fixed in 6.0.7. Earlier versions of this advisory incorrectly stated that other versions were affected.*",
   "affected": [
     {
       "package": {