<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 19 Oct 2026 11:12:44 +0000</lastBuildDate>
    <item>
      <title>cbc7988b-9eb2-4d04-ba42-5ada0df4e34b</title>
      <link>https://vulnerability.circl.lu/sighting/cbc7988b-9eb2-4d04-ba42-5ada0df4e34b/export</link>
      <description>{"uuid": "cbc7988b-9eb2-4d04-ba42-5ada0df4e34b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-9268", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/2evqwqlyisig4", "content": "CVE-2026-9268 - Incorrect Authorization in GitLab\nCVE ID : CVE-2026-9268\n \n Published : Oct. 13, 2026, 2:17 a.m. | 13\u00a0minutes ago\n \n Description : GitLab has remediated an issue in GitLab EE affecting all versions from 13.6 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19...", "creation_timestamp": "2026-10-13T03:43:12.476780Z"}</description>
      <content:encoded>{"uuid": "cbc7988b-9eb2-4d04-ba42-5ada0df4e34b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-9268", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/2evqwqlyisig4", "content": "CVE-2026-9268 - Incorrect Authorization in GitLab\nCVE ID : CVE-2026-9268\n \n Published : Oct. 13, 2026, 2:17 a.m. | 13\u00a0minutes ago\n \n Description : GitLab has remediated an issue in GitLab EE affecting all versions from 13.6 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19...", "creation_timestamp": "2026-10-13T03:43:12.476780Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/cbc7988b-9eb2-4d04-ba42-5ada0df4e34b/export</guid>
      <pubDate>Tue, 13 Oct 2026 03:43:12 +0000</pubDate>
    </item>
    <item>
      <title>9a084633-5f07-4fb6-964c-1fd94c905082</title>
      <link>https://vulnerability.circl.lu/sighting/9a084633-5f07-4fb6-964c-1fd94c905082/export</link>
      <description>{"uuid": "9a084633-5f07-4fb6-964c-1fd94c905082", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-9268", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117431180098740059", "content": "CVE-2026-9268 Incorrect Authorization in GitLab GitLab has remediated an issue in GitLab EE affecting all versions from 13.6 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user with limited permissions to modify project CI/CD deployment rollback settings without proper authorization, due to insufficient access control checks.\nhttps://www.cve.org/CVERecord?id=CVE-2026-9268https://gitlab.com/gitlab-org/gitlab/-/work_items/600934https://hackerone.com/reports/3687442https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/#gitlab #GitLab#CVE_2026_9268#bot", "creation_timestamp": "2026-10-13T02:13:26.938889Z"}</description>
      <content:encoded>{"uuid": "9a084633-5f07-4fb6-964c-1fd94c905082", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-9268", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117431180098740059", "content": "CVE-2026-9268 Incorrect Authorization in GitLab GitLab has remediated an issue in GitLab EE affecting all versions from 13.6 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user with limited permissions to modify project CI/CD deployment rollback settings without proper authorization, due to insufficient access control checks.\nhttps://www.cve.org/CVERecord?id=CVE-2026-9268https://gitlab.com/gitlab-org/gitlab/-/work_items/600934https://hackerone.com/reports/3687442https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/#gitlab #GitLab#CVE_2026_9268#bot", "creation_timestamp": "2026-10-13T02:13:26.938889Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/9a084633-5f07-4fb6-964c-1fd94c905082/export</guid>
      <pubDate>Tue, 13 Oct 2026 02:13:26 +0000</pubDate>
    </item>
    <item>
      <title>387a055d-323f-4611-b72f-d626a4f8c9a2</title>
      <link>https://vulnerability.circl.lu/sighting/387a055d-323f-4611-b72f-d626a4f8c9a2/export</link>
      <description>{"uuid": "387a055d-323f-4611-b72f-d626a4f8c9a2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-92681", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mxpaevpdcv2o", "content": "CVE-2026-92681\nVersions of the Neo4j GraphQL library up to 7.6.3 ignore security rules placed on the overall schema or on the Query/Mutation types when a top\u2011level field runs a custom database query (Cypher). This means\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#CVE #infosec", "creation_timestamp": "2026-10-12T19:20:04.939838Z"}</description>
      <content:encoded>{"uuid": "387a055d-323f-4611-b72f-d626a4f8c9a2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-92681", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mxpaevpdcv2o", "content": "CVE-2026-92681\nVersions of the Neo4j GraphQL library up to 7.6.3 ignore security rules placed on the overall schema or on the Query/Mutation types when a top\u2011level field runs a custom database query (Cypher). This means\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#CVE #infosec", "creation_timestamp": "2026-10-12T19:20:04.939838Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/387a055d-323f-4611-b72f-d626a4f8c9a2/export</guid>
      <pubDate>Mon, 12 Oct 2026 19:20:04 +0000</pubDate>
    </item>
    <item>
      <title>f744fbba-6d71-47f4-be67-d63495b65951</title>
      <link>https://vulnerability.circl.lu/sighting/f744fbba-6d71-47f4-be67-d63495b65951/export</link>
      <description>{"uuid": "f744fbba-6d71-47f4-be67-d63495b65951", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-92681", "type": "seen", "source": "https://bsky.app/profile/stemshop.bsky.social/post/3mxp4etjpeb2q", "content": "\ud83d\udea8 CVE-2026-92681 \u2014 CVSS 9.3 CRITICAL\n\nIn @neo4j/graphql versions up to and including 7.6.3, @authentication directives applied at the schema leve...\n\n\ud83d\udd0e https://stemshop.top/cve/CVE-2026-92681\n\n#CVE #CyberSecurity #InfoSec", "creation_timestamp": "2026-10-12T18:08:26.756186Z"}</description>
      <content:encoded>{"uuid": "f744fbba-6d71-47f4-be67-d63495b65951", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-92681", "type": "seen", "source": "https://bsky.app/profile/stemshop.bsky.social/post/3mxp4etjpeb2q", "content": "\ud83d\udea8 CVE-2026-92681 \u2014 CVSS 9.3 CRITICAL\n\nIn @neo4j/graphql versions up to and including 7.6.3, @authentication directives applied at the schema leve...\n\n\ud83d\udd0e https://stemshop.top/cve/CVE-2026-92681\n\n#CVE #CyberSecurity #InfoSec", "creation_timestamp": "2026-10-12T18:08:26.756186Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/f744fbba-6d71-47f4-be67-d63495b65951/export</guid>
      <pubDate>Mon, 12 Oct 2026 18:08:26 +0000</pubDate>
    </item>
    <item>
      <title>d36bb085-ef7f-4e76-86ff-6b989191ea4d</title>
      <link>https://vulnerability.circl.lu/sighting/d36bb085-ef7f-4e76-86ff-6b989191ea4d/export</link>
      <description>{"uuid": "d36bb085-ef7f-4e76-86ff-6b989191ea4d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2026-9268", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/gitlab-multiple-vulnerabilities_20261013", "content": "", "creation_timestamp": "2026-10-12T18:00:00.000000Z"}</description>
      <content:encoded>{"uuid": "d36bb085-ef7f-4e76-86ff-6b989191ea4d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2026-9268", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/gitlab-multiple-vulnerabilities_20261013", "content": "", "creation_timestamp": "2026-10-12T18:00:00.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/d36bb085-ef7f-4e76-86ff-6b989191ea4d/export</guid>
      <pubDate>Mon, 12 Oct 2026 18:00:00 +0000</pubDate>
    </item>
    <item>
      <title>1d79f9c2-e873-4ea3-8917-b974e7fa5550</title>
      <link>https://vulnerability.circl.lu/sighting/1d79f9c2-e873-4ea3-8917-b974e7fa5550/export</link>
      <description>{"uuid": "1d79f9c2-e873-4ea3-8917-b974e7fa5550", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-92682", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117428689857788460", "content": "CVE-2026-92682 @neo4j/graphql: authorization relationship and connection filters invert the \"none\" quantifier In @neo4j/graphql versions from 7.0.0 up to but not including 7.6.4, the none quantifier in @authorization filters on relationships and connections is not negated when translated to Cypher, so it behaves like some. A rule such as \"none of the related denied users matches the JWT subject\" therefore returns exactly the records it was meant to exclude, and excludes those it was meant to return. An authenticated user whom such a rule is meant to deny can read the protected records. This is also the case for mutations, so the impact is that sensitive data could also be created and deleted by users that shouldn't have access according to the typedefs. Fixed in 7.6.4.\nhttps://www.cve.org/CVERecord?id=CVE-2026-92682https://github.com/neo4j/graphql/security/advisories/GHSA-h873-p2wr-fjx6https://github.com/neo4j/graphql/commit/17650cc370445a6bb9d394d34063d3623e987aa2https://github.com/neo4j/graphql/releases/tag/%40neo4j%2Fgraphql%407.6.4https://www.npmjs.com/package/@neo4j/graphql#Neo4j #@neo4j/graphql#CVE_2026_92682#bot", "creation_timestamp": "2026-10-12T15:40:08.926380Z"}</description>
      <content:encoded>{"uuid": "1d79f9c2-e873-4ea3-8917-b974e7fa5550", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-92682", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117428689857788460", "content": "CVE-2026-92682 @neo4j/graphql: authorization relationship and connection filters invert the \"none\" quantifier In @neo4j/graphql versions from 7.0.0 up to but not including 7.6.4, the none quantifier in @authorization filters on relationships and connections is not negated when translated to Cypher, so it behaves like some. A rule such as \"none of the related denied users matches the JWT subject\" therefore returns exactly the records it was meant to exclude, and excludes those it was meant to return. An authenticated user whom such a rule is meant to deny can read the protected records. This is also the case for mutations, so the impact is that sensitive data could also be created and deleted by users that shouldn't have access according to the typedefs. Fixed in 7.6.4.\nhttps://www.cve.org/CVERecord?id=CVE-2026-92682https://github.com/neo4j/graphql/security/advisories/GHSA-h873-p2wr-fjx6https://github.com/neo4j/graphql/commit/17650cc370445a6bb9d394d34063d3623e987aa2https://github.com/neo4j/graphql/releases/tag/%40neo4j%2Fgraphql%407.6.4https://www.npmjs.com/package/@neo4j/graphql#Neo4j #@neo4j/graphql#CVE_2026_92682#bot", "creation_timestamp": "2026-10-12T15:40:08.926380Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/1d79f9c2-e873-4ea3-8917-b974e7fa5550/export</guid>
      <pubDate>Mon, 12 Oct 2026 15:40:08 +0000</pubDate>
    </item>
    <item>
      <title>df7dded3-fb16-4602-bc91-52289cb53602</title>
      <link>https://vulnerability.circl.lu/sighting/df7dded3-fb16-4602-bc91-52289cb53602/export</link>
      <description>{"uuid": "df7dded3-fb16-4602-bc91-52289cb53602", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-92681", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117428687216536693", "content": "CVE-2026-92681 @neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields In @neo4j/graphql versions up to and including 7.6.3, @authentication directives applied at the schema level or on the Query or Mutation types are silently ignored for top-level fields annotated with @cypher. Only @authentication directives placed directly on the individual fields are enforced. An application that exposes a top-level @cypher field and relies on schema-level or type-level @authentication to protect it allows unauthenticated callers to invoke the field and run the configured Cypher statement with the privileges of the GraphQL service account, which may permit reading and modifying data. Fixed in 7.6.4.\nhttps://www.cve.org/CVERecord?id=CVE-2026-92681https://github.com/neo4j/graphql/security/advisories/GHSA-8xj4-8gg9-fx9hhttps://github.com/neo4j/graphql/commit/ef69cc69ff5e97c60d64aa524005f939c5ba3633https://github.com/neo4j/graphql/releases/tag/%40neo4j%2Fgraphql%407.6.4https://www.npmjs.com/package/@neo4j/graphql#Neo4j #@neo4j/graphql#CVE_2026_92681#bot", "creation_timestamp": "2026-10-12T15:39:29.143339Z"}</description>
      <content:encoded>{"uuid": "df7dded3-fb16-4602-bc91-52289cb53602", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-92681", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117428687216536693", "content": "CVE-2026-92681 @neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields In @neo4j/graphql versions up to and including 7.6.3, @authentication directives applied at the schema level or on the Query or Mutation types are silently ignored for top-level fields annotated with @cypher. Only @authentication directives placed directly on the individual fields are enforced. An application that exposes a top-level @cypher field and relies on schema-level or type-level @authentication to protect it allows unauthenticated callers to invoke the field and run the configured Cypher statement with the privileges of the GraphQL service account, which may permit reading and modifying data. Fixed in 7.6.4.\nhttps://www.cve.org/CVERecord?id=CVE-2026-92681https://github.com/neo4j/graphql/security/advisories/GHSA-8xj4-8gg9-fx9hhttps://github.com/neo4j/graphql/commit/ef69cc69ff5e97c60d64aa524005f939c5ba3633https://github.com/neo4j/graphql/releases/tag/%40neo4j%2Fgraphql%407.6.4https://www.npmjs.com/package/@neo4j/graphql#Neo4j #@neo4j/graphql#CVE_2026_92681#bot", "creation_timestamp": "2026-10-12T15:39:29.143339Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/df7dded3-fb16-4602-bc91-52289cb53602/export</guid>
      <pubDate>Mon, 12 Oct 2026 15:39:29 +0000</pubDate>
    </item>
  </channel>
</rss>
