<?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>Sun, 11 Oct 2026 22:14:31 +0000</lastBuildDate>
    <item>
      <title>a884baee-f438-40a5-978f-8effb21cdb1c</title>
      <link>https://vulnerability.circl.lu/sighting/a884baee-f438-40a5-978f-8effb21cdb1c/export</link>
      <description>{"uuid": "a884baee-f438-40a5-978f-8effb21cdb1c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-108711", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117422311105481470", "content": "CVE-2026-108711 Plastic Labs Honcho through 3.3.0 Incorrect Authorization via POST /v3/workspaces Plastic Labs Honcho through 3.3.0 contains an incorrect authorization vulnerability that allows peer- or session-scoped API key holders to read workspace data because get_or_create_workspace checks only the workspace claim. Attackers can submit their parent workspace name to the POST /v3/workspaces endpoint to retrieve workspace metadata and configuration, including custom_instructions, reserved for workspace or admin keys.\nhttps://www.cve.org/CVERecord?id=CVE-2026-108711https://hackmd.io/@haind/honcho-scoped-jwt-workspace-config-disclosurehttps://github.com/plastic-labs/honcho/blob/608aec8a928da13c540262ed980c569448fb53ab/src/routers/workspaces.py#L41-L72https://github.com/plastic-labs/honcho/blob/608aec8a928da13c540262ed980c569448fb53ab/src/security.py#L218-L225https://github.com/plastic-labs/honcho/blob/608aec8a928da13c540262ed980c569448fb53ab/src/crud/workspace.py#L112-L119https://github.com/plastic-labs/honchohttps://www.vulncheck.com/advisories/plastic-labs-honcho-through-3.3.0-incorrect-authorization-via-post-v3-workspaces#PlasticLabs #honcho#CVE_2026_108711#bot", "creation_timestamp": "2026-10-11T12:37:57.044022Z"}</description>
      <content:encoded>{"uuid": "a884baee-f438-40a5-978f-8effb21cdb1c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-108711", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117422311105481470", "content": "CVE-2026-108711 Plastic Labs Honcho through 3.3.0 Incorrect Authorization via POST /v3/workspaces Plastic Labs Honcho through 3.3.0 contains an incorrect authorization vulnerability that allows peer- or session-scoped API key holders to read workspace data because get_or_create_workspace checks only the workspace claim. Attackers can submit their parent workspace name to the POST /v3/workspaces endpoint to retrieve workspace metadata and configuration, including custom_instructions, reserved for workspace or admin keys.\nhttps://www.cve.org/CVERecord?id=CVE-2026-108711https://hackmd.io/@haind/honcho-scoped-jwt-workspace-config-disclosurehttps://github.com/plastic-labs/honcho/blob/608aec8a928da13c540262ed980c569448fb53ab/src/routers/workspaces.py#L41-L72https://github.com/plastic-labs/honcho/blob/608aec8a928da13c540262ed980c569448fb53ab/src/security.py#L218-L225https://github.com/plastic-labs/honcho/blob/608aec8a928da13c540262ed980c569448fb53ab/src/crud/workspace.py#L112-L119https://github.com/plastic-labs/honchohttps://www.vulncheck.com/advisories/plastic-labs-honcho-through-3.3.0-incorrect-authorization-via-post-v3-workspaces#PlasticLabs #honcho#CVE_2026_108711#bot", "creation_timestamp": "2026-10-11T12:37:57.044022Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/a884baee-f438-40a5-978f-8effb21cdb1c/export</guid>
      <pubDate>Sun, 11 Oct 2026 12:37:57 +0000</pubDate>
    </item>
  </channel>
</rss>
