CVE-2026-92759 json
SecObserve before 1.59.1 Information Disclosure via API Configuration
published last mo. modified last mo. also EUVD-2026-81027 , GHSA-r968-78vw-jj9m
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository SecObserve/SecObserve. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
SecObserve versions before 1.59.1 contain an information disclosure vulnerability in the ApiConfigurationSerializer that fails to strip the basic_auth_password field from API configuration responses. View-only product members can retrieve the decrypted basic-auth password of configured scanner or integration service accounts through standard REST endpoints.
Patch / fix
Is CVE-2026-92759 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- SecObserve SecObserve
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
github.com
/SecObserve/SecObserve/security/advisories/GHSA-r968-78vw-jj9m
third-party-advisory, vendor-advisory, advisory
-
github.com
/SecObserve/SecObserve/issues/4799
issue-tracking
-
github.com
/SecObserve/SecObserve
product
-
github.com
/SecObserve/SecObserve/blob/v1.54.0/backend/application/import_observations/api/serializers.py#L103-L119
technical-description
-
github.com
/SecObserve/SecObserve/releases/tag/v1.59.1
release-notes
-
vulncheck.com
/advisories/secobserve-before-1.59.1-information-disclosure-via-api-configuration
third-party-advisory
Sources
- CVE List CVE-2026-92759
- NVD CVE-2026-92759
- Maintainer advisory GHSA-r968-78vw-jj9m
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of SecObserve/SecObserve published their own advisory on GitHub. Reviewed sources take precedence over it.