{ "document": { "category": "csaf_base", "csaf_version": "2.0", "distribution": { "tlp": { "label": "WHITE" } }, "lang": "en", "notes": [ { "category": "legal_disclaimer", "text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this portal to enhance access to its information and vulnerabilities. The use of this information is subject to the following terms and conditions:\n\nThe vulnerabilities disclosed in this portal are gathered by NCSC-NL from a variety of open sources, which the user can retrieve from other platforms. NCSC-NL makes every reasonable effort to ensure that the content of this portal is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or real-time keeping up-to-date. NCSC-NL does not control nor guarantee the accuracy, relevance, timeliness or completeness of information obtained from these external sources. The vulnerabilities disclosed in this portal are intended solely for the convenience of professional parties to take appropriate measures to manage the risks posed to the cybersecurity. No rights can be derived from the information provided therein.\n\nNCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of the vulnerabilities disclosed in this portal. This includes damage resulting from the inaccuracy of incompleteness of the information contained in it.\nThe information on this page is subject to Dutch law. All disputes related to or arising from the use of this portal regarding the disclosure of vulnerabilities will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings." } ], "publisher": { "category": "coordinator", "contact_details": "cert@ncsc.nl", "name": "National Cyber Security Centre", "namespace": "https://www.ncsc.nl/" }, "title": "CVE-2026-32694", "tracking": { "current_release_date": "2026-03-25T18:24:38.685973Z", "generator": { "date": "2026-02-17T15:00:00Z", "engine": { "name": "V.E.L.M.A", "version": "1.7" } }, "id": "CVE-2026-32694", "initial_release_date": "2026-03-18T13:38:42.835030Z", "revision_history": [ { "date": "2026-03-18T13:38:42.835030Z", "number": "1", "summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products connected (1).| References created (1).| CWES updated (1)." }, { "date": "2026-03-18T13:38:52.351383Z", "number": "2", "summary": "NCSC Score created." }, { "date": "2026-03-18T14:29:13.164532Z", "number": "3", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (1).| CWES updated (1)." }, { "date": "2026-03-18T14:29:19.143041Z", "number": "4", "summary": "NCSC Score updated." }, { "date": "2026-03-18T14:39:17.335610Z", "number": "5", "summary": "Unknown change." }, { "date": "2026-03-18T15:50:30.714139Z", "number": "6", "summary": "NCSC Score updated." }, { "date": "2026-03-20T03:41:21.611661Z", "number": "7", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products connected (1).| Product Identifiers created (1).| Exploits created (1).| References created (1).| CWES updated (1)." }, { "date": "2026-03-20T03:41:24.609209Z", "number": "8", "summary": "NCSC Score updated." }, { "date": "2026-03-20T09:29:45.297549Z", "number": "9", "summary": "Source connected.| CVE status created. (valid)| EPSS created." }, { "date": "2026-03-20T18:16:26.680636Z", "number": "10", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (4).| CWES updated (1)." }, { "date": "2026-03-20T18:16:30.470914Z", "number": "11", "summary": "NCSC Score updated." }, { "date": "2026-03-25T18:13:11.879040Z", "number": "12", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (1).| References created (3).| CWES updated (1)." }, { "date": "2026-03-25T18:13:13.612246Z", "number": "13", "summary": "NCSC Score updated." }, { "date": "2026-03-25T18:13:27.565514Z", "number": "14", "summary": "Source created.| CVE status created. (valid)| Description created for source.| References created (3)." } ], "status": "interim", "version": "14" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:semver/3.0.0|<3.6.19", "product": { "name": "vers:semver/3.0.0|<3.6.19", "product_id": "CSAFPID-5843880" } }, { "category": "product_version_range", "name": "vers:unknown/>=3.0.0|<3.6.19", "product": { "name": "vers:unknown/>=3.0.0|<3.6.19", "product_id": "CSAFPID-5866182", "product_identification_helper": { "cpe": "cpe:2.3:a:canonical:juju:*:*:*:*:*:*:*:*" } } } ], "category": "product_name", "name": "Juju" } ], "category": "vendor", "name": "Canonical" }, { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:unknown/>=0.0.0-20221021155847-35c560704ee2|<0.0.0-20260319091847-d06919eb03ec", "product": { "name": "vers:unknown/>=0.0.0-20221021155847-35c560704ee2|<0.0.0-20260319091847-d06919eb03ec", "product_id": "CSAFPID-5907232" } } ], "category": "product_name", "name": "juju" } ], "category": "vendor", "name": "juju" } ] }, "vulnerabilities": [ { "cve": "CVE-2026-32694", "cwe": { "id": "CWE-343", "name": "Predictable Value Range from Previous Values" }, "notes": [ { "category": "description", "text": "In Juju from version 3.0.0 through 3.6.18, when a secret owner grants permissions to a secret to a grantee, the secret owner relies exclusively on a predictable XID of the secret to verify ownership. This allows a malicious grantee which can request secrets to predict past secrets granted by the same secret owner to different grantees, allowing them to use the resources granted by those past secrets. Successful exploitation relies on a very specific configuration, specific data semantic, and the administrator having the need to deploy at least two different applications, one of them controlled by the attacker.", "title": "cveprojectv5 - https://www.cve.org/CVERecord?id=CVE-2026-32694" }, { "category": "description", "text": "In Juju from version 3.0.0 through 3.6.18, when a secret owner grants permissions to a secret to a grantee, the secret owner relies exclusively on a predictable XID of the secret to verify ownership. This allows a malicious grantee which can request secrets to predict past secrets granted by the same secret owner to different grantees, allowing them to use the resources granted by those past secrets. Successful exploitation relies on a very specific configuration, specific data semantic, and the administrator having the need to deploy at least two different applications, one of them controlled by the attacker.", "title": "nvd - https://nvd.nist.gov/vuln/detail/CVE-2026-32694" }, { "category": "description", "text": "In Juju from version 3.0.0 through 3.6.18, when a secret owner grants permissions to a secret to a grantee, the secret owner relies exclusively on a predictable XID of the secret to verify ownership. This allows a malicious grantee which can request secrets to predict past secrets granted by the same secret owner to different grantees, allowing them to use the resources granted by those past secrets. Successful exploitation relies on a very specific configuration, specific data semantic, and the administrator having the need to deploy at least two different applications, one of them controlled by the attacker.", "title": "nvd - https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-32694" }, { "category": "description", "text": "### Summary\n\nPredictable secret ID and lack of secret origin API enable confused deputy attacks on Juju workloads.\n\n### Details\n\nA Juju application can create a secret and grant it to another integrated application (grantee).\n\nWhen they do so, the secret owner has to communicate the secret id to the grantee.\n\nThe grantee, having received the secret id can load the secret content and perform operations on behalf of the secret owner.\n\nHowever, today the grantee has no way to determine which granted secret belongs to which owner.\n\nInstead the grantee relies on:\n- being able to read the secret by id (secret was in fact granted, by some entity)\n- secret id was received over a relation (the remote end of the relation is presumed to be secret owner)\n\nAdditionally, secret IDs are XID, which are predictable, here two secrets created by two distinct apps in the same K8s model close in time:\n```\nd34vsl7mp25c76301hs0\ntime (UTC): 2025-09-17 00:18:28 (Unix 1758068308)\nmachine: f6c88a\npid: 50072\ncounter: 6294648\n\nd34vslfmp25c76301hsg\ntime (UTC): 2025-09-17 00:18:29 (Unix 1758068309)\nmachine: f6c88a\npid: 50072\ncounter: 6294649\n```\n\n### PoC\n\nThis allows for an IDOR attack where:\n- actors:\n - a **Good** application (the owner of the _Victim_),\n - an **Evil** application, and\n - a **Provider** application (the _Confused Deputy_)\n- relations: **Good** --- **Provider**, **Evil** --- **Provider**\n- secrets: **Good** and **Evil** create _Secrets_, granting them to the **Provider** and communicate _Secret IDs_ with the **Provider**.\n- semantics: the **Provider** performs some operation on behalf of the **Good**/**Evil** using the _Secret_.\n- weakness 1: **Evil** can guess the _Secret ID_ that **Good** granted and communicated to **Provider**.\n- weakness 2: _Juju_ doesn't provide the **Provider** application the facility to verify the provenance of the _Secret IDs_.\n- exploit: **Evil** passes **Good**'s secret id to **Provider**.\n- bypass: **Provider** performs _evil_ operation with **Good**'s _Secret ID_ on behalf of **Evil**.\n\n**Evil** could benefit by:\n- exfiltrating **Good**'s _Secret_ via reflection.\n- reading or mutating **Good**'s resources accessible via **Good*'s _Secret_.\n\n### Impact\n\nThis requires a complex setup.\n\nNot all shared secrets are used like above, so an actual exploit requires a very specific relation interface, specific semantics of the data in the databag, and an administrator having a reasonable need to deploy two apps (one evil, one good) related to the same (third) provider app.\n\nIf exploited, it can be very hard to determine what went wrong after the fact.\n\n### Suggested remediation\n\n#### 1. Longer, random secret IDs\n\nFor example, if the secret id was extended with a 128-bit nonce, guessing a sibling secret ID would be infeasible, and an attack of this style would require another weakness (e.g. secret IDs exposed in logs)\n\n#### 2. Grantee secret API\n\nToday, an app is not allowed to call `secret-info-get` on the granted secret.\nAdditionally, granted secrets are not included in the `secret-ids` output.\n\nSuppose that the Provider could run these hook tools:\n```command\n(provider/0)> secret-ids\nmy-own-secret-123\n\n(provider/0)> secret-ids --grants\ngood-secret-id-42\nevil-secret-id-43\n\n(provider/0)> secret-info-get good-secret-id-42\ngood-secret-id-42:\n revision: 1\n label: \"\"\n owner: good\n grant-relation-id: 12\n rotation: never\n```\n\nThe Provider would then able to validate the secret ID it's about to use against:\n- the relation in which the secret ID has been passed (good relation 12 or evil relation 14)\n- the application or unit name of the secret owner (good or evil)", "title": "github - https://api.github.com/advisories/GHSA-5cj2-rqqf-hx9p" }, { "category": "description", "text": "### Summary\n\nPredictable secret ID and lack of secret origin API enable confused deputy attacks on Juju workloads.\n\n### Details\n\nA Juju application can create a secret and grant it to another integrated application (grantee).\n\nWhen they do so, the secret owner has to communicate the secret id to the grantee.\n\nThe grantee, having received the secret id can load the secret content and perform operations on behalf of the secret owner.\n\nHowever, today the grantee has no way to determine which granted secret belongs to which owner.\n\nInstead the grantee relies on:\n- being able to read the secret by id (secret was in fact granted, by some entity)\n- secret id was received over a relation (the remote end of the relation is presumed to be secret owner)\n\nAdditionally, secret IDs are XID, which are predictable, here two secrets created by two distinct apps in the same K8s model close in time:\n```\nd34vsl7mp25c76301hs0\ntime (UTC): 2025-09-17 00:18:28 (Unix 1758068308)\nmachine: f6c88a\npid: 50072\ncounter: 6294648\n\nd34vslfmp25c76301hsg\ntime (UTC): 2025-09-17 00:18:29 (Unix 1758068309)\nmachine: f6c88a\npid: 50072\ncounter: 6294649\n```\n\n### PoC\n\nThis allows for an IDOR attack where:\n- actors:\n - a **Good** application (the owner of the _Victim_),\n - an **Evil** application, and\n - a **Provider** application (the _Confused Deputy_)\n- relations: **Good** --- **Provider**, **Evil** --- **Provider**\n- secrets: **Good** and **Evil** create _Secrets_, granting them to the **Provider** and communicate _Secret IDs_ with the **Provider**.\n- semantics: the **Provider** performs some operation on behalf of the **Good**/**Evil** using the _Secret_.\n- weakness 1: **Evil** can guess the _Secret ID_ that **Good** granted and communicated to **Provider**.\n- weakness 2: _Juju_ doesn't provide the **Provider** application the facility to verify the provenance of the _Secret IDs_.\n- exploit: **Evil** passes **Good**'s secret id to **Provider**.\n- bypass: **Provider** performs _evil_ operation with **Good**'s _Secret ID_ on behalf of **Evil**.\n\n**Evil** could benefit by:\n- exfiltrating **Good**'s _Secret_ via reflection.\n- reading or mutating **Good**'s resources accessible via **Good*'s _Secret_.\n\n### Impact\n\nThis requires a complex setup.\n\nNot all shared secrets are used like above, so an actual exploit requires a very specific relation interface, specific semantics of the data in the databag, and an administrator having a reasonable need to deploy two apps (one evil, one good) related to the same (third) provider app.\n\nIf exploited, it can be very hard to determine what went wrong after the fact.\n\n### Suggested remediation\n\n#### 1. Longer, random secret IDs\n\nFor example, if the secret id was extended with a 128-bit nonce, guessing a sibling secret ID would be infeasible, and an attack of this style would require another weakness (e.g. secret IDs exposed in logs)\n\n#### 2. Grantee secret API\n\nToday, an app is not allowed to call `secret-info-get` on the granted secret.\nAdditionally, granted secrets are not included in the `secret-ids` output.\n\nSuppose that the Provider could run these hook tools:\n```command\n(provider/0)> secret-ids\nmy-own-secret-123\n\n(provider/0)> secret-ids --grants\ngood-secret-id-42\nevil-secret-id-43\n\n(provider/0)> secret-info-get good-secret-id-42\ngood-secret-id-42:\n revision: 1\n label: \"\"\n owner: good\n grant-relation-id: 12\n rotation: never\n```\n\nThe Provider would then able to validate the secret ID it's about to use against:\n- the relation in which the secret ID has been passed (good relation 12 or evil relation 14)\n- the application or unit name of the secret owner (good or evil)", "title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGHSA-5cj2-rqqf-hx9p.json?alt=media" }, { "category": "description", "text": "Juju affected by Confused Deputy IDOR attack via Predictable user specified ID in Juju Secrets in github.com/juju/juju", "title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGO-2026-4778.json?alt=media" }, { "category": "other", "text": "0.00029", "title": "EPSS" }, { "category": "other", "text": "4.4", "title": "NCSC Score" }, { "category": "other", "text": "Is related to a product by vendor Canonical", "title": "NCSC Score top increasing factors" }, { "category": "other", "text": "Is related to (a version of) an uncommon product, Exploit code publicly available, There is exploit data available from source Nvd", "title": "NCSC Score top decreasing factors" } ], "product_status": { "known_affected": [ "CSAFPID-5843880", "CSAFPID-5866182", "CSAFPID-5907232" ] }, "references": [ { "category": "external", "summary": "Source - cveprojectv5", "url": "https://www.cve.org/CVERecord?id=CVE-2026-32694" }, { "category": "external", "summary": "Source raw - cveprojectv5", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/32xxx/CVE-2026-32694.json" }, { "category": "external", "summary": "Source - nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32694" }, { "category": "external", "summary": "Source raw - nvd", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-32694" }, { "category": "external", "summary": "Source - nvd", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-32694" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Source - github", "url": "https://api.github.com/advisories/GHSA-5cj2-rqqf-hx9p" }, { "category": "external", "summary": "Source - osv", "url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGHSA-5cj2-rqqf-hx9p.json?alt=media" }, { "category": "external", "summary": "Source - osv", "url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGO-2026-4778.json?alt=media" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://github.com/juju/juju/security/advisories/GHSA-5cj2-rqqf-hx9p" }, { "category": "external", "summary": "Reference - github; osv", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32694" }, { "category": "external", "summary": "Reference - github; osv", "url": "https://github.com/juju/juju/commit/d06919eb03ec68156818bcc304b5fe1c39a8f9e9" }, { "category": "external", "summary": "Reference - github", "url": "https://github.com/advisories/GHSA-5cj2-rqqf-hx9p" } ], "scores": [ { "cvss_v3": { "version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H", "baseScore": 6.6, "baseSeverity": "MEDIUM" }, "products": [ "CSAFPID-5843880", "CSAFPID-5866182", "CSAFPID-5907232" ] } ], "title": "CVE-2026-32694" } ] }