Security readout for executives and security teams
Plain-English summary
RustFS alpha versions can write a shared RPC signing secret into logs when an invalid RPC signature is received. Anyone who can read those logs could use the exposed secret to impersonate trusted RPC calls. The issue is fixed in RustFS 1.0.0-alpha.80.
Executive priority
Treat as targeted cleanup rather than emergency response. Prioritize upgrades where RustFS alpha builds handle sensitive storage operations or logs are broadly accessible. Rotate secrets if log exposure is plausible.
Technical view
CVE-2026-22782 is a CWE-532 sensitive-information-in-log flaw in RustFS RPC authentication. In affected versions >=1.0.0-alpha.1 and <1.0.0-alpha.80, the invalid signature branch in crates/ecstore/src/rpc/http_auth.rs logs the shared HMAC secret and expected signature. RPC and admin request handlers can reach this code path.
Likely exposure
Exposure is limited to RustFS deployments running affected alpha versions, especially where RustFS logs are readable by users, operators, log aggregation systems, or third-party monitoring tools beyond the trusted service boundary.
Exploitation context
The source states any invalidly signed request can trigger the logging path. Public sources do not indicate active exploitation, and the CVE is not marked KEV. Practical impact depends on whether attackers can cause invalid requests and later access resulting logs.
Researcher notes
The advisory identifies the vulnerable file and fixed version. The available evidence supports low severity because confidentiality impact is limited and depends on log access. Do not assume broader RustFS versions or active exploitation beyond the cited sources.
Mitigation direction
- Upgrade RustFS to 1.0.0-alpha.80 or later.
- Restrict access to RustFS logs and centralized log platforms.
- Review vendor advisory and commit for deployment-specific guidance.
- Rotate exposed shared HMAC secrets if affected logs may have been accessed.
Validation and detection
- Inventory RustFS versions and identify any versions before 1.0.0-alpha.80.
- Check whether RPC or admin handlers are enabled in affected deployments.
- Review log retention and access permissions for RustFS logs.
- Search historical logs for accidentally recorded HMAC secrets using approved internal procedures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-532: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-22782 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 2.9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
2.9LowVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/rustfs/rustfs/security/advisories/GHSA-333v-68xh-8mmqCVE reference · x_refsource_CONFIRM
- https://github.com/rustfs/rustfs/commit/6b2eebee1d07399ef02c0863bd515b4412a5a560CVE reference · x_refsource_MISC
- https://github.com/rustfs/rustfs/blob/9e162b6e9ebb874cc1d06a7b33bc4a05786578aa/crates/ecstore/src/rpc/http_auth.rs#L115-L122CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information into Log File
Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.