Answer in brief
CVE-2023-2878 records a Medium severity (CVSS 6.5) vulnerability in secrets-store-csi-driver discloses service account tokens in logs. The current sources do not mark it as known exploited. The current feed maps sigs.k8s.io/secrets-store-csi-driver (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps sigs.k8s.io/secrets-store-csi-driver (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| sigs.k8s.io/secrets-store-csi-drivergo | >=0 <1.3.3 | 1.3.3 |
Published upstream
May 26, 2023
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Sep 10, 2026
A security issue was discovered in secrets-store-csi-driver where an actor with access to the driver logs could observe service account tokens. These tokens could then potentially be exchanged with external cloud providers to access secrets stored in cloud vault solutions. Tokens are only logged when [TokenRequests is configured in the CSIDriver object](https://kubernetes-csi.github.io/docs/token-requests.html) and the driver is set to run at log level 2 or greater via the -v flag. This issue has been rated MEDIUM [CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) (6.5), and assigned CVE-2023-2878 ### Am I vulnerable? You may be vulnerable if [TokenRequests is configured in the CSIDriver object](https://kubernetes-csi.github.io/docs/token-requests.html) and the driver is set to run at log level 2 or greater via the -v flag. To check if token requests are configured, run the following command: ```bash kubectl get csidriver secrets-store.csi.k8s.io -o jsonpath="{.spec.tokenRequests}" ``` To check if tokens are being logged, examine the secrets-store container log: ```bash kubectl logs -l app=secrets-store-csi-driver -c secrets-store -f | grep --line-buffered "csi.storage.k8s.io/serviceAccount.tokens" ``` ### Affected Versions - secrets-store-csi-driver < 1.3.3 ### How do I mitigate this vulnerability? Prior to upgrading, this vulnerability can be mitigated by running secrets-store-csi-driver at log level 0 or 1 via the -v flag. ### Fixed Versions - secrets-store-csi-driver >= 1.3.3 To upgrade, refer to the documentation: https://secrets-store-csi-driver.sigs.k8s.io/getting-started/upgrades.html#upgrades ### Detection Examine cloud provider logs for unexpected token exchanges, as well as unexpected access to cloud vault secrets. If you find evidence that this vulnerability has been exploited, please contact [[email protected]](https://groups.google.com/)
Quoted source text, attributed separately from HOL analysis.