CVE-2026-83308: bi-publisher
Affects bi-publisherSource GCVE Database
Not known to be exploited · CVSS 8.1 High.
Data as of 30 Oct 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavencom.oracle/bi-publisherpkg:maven/com.oracle/bi-publisherOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Oracle has released security patches for this vulnerability in the September 2026 Critical Security Patch Update. Users should apply the official patches promptly to remediate the issue. Oracle strongly recommends remaining on actively-supported versions and applying security patches without delay. No alternative mitigations or workarounds are specified in the advisory.
Description
A vulnerability in Oracle BI Publisher (component of Oracle Analytics) allows a low privileged attacker with network access via SOAP to compromise the system. Affected versions include 8.2.0.0.0, 12.2.1.4.0, and 26.1.0.0.0. The vulnerability can lead to unauthorized creation, deletion, or modification of critical data and can cause denial of service by hanging or crashing the application. The CVSS 3.1 base score is 8.1, indicating high severity with impacts on integrity and availability. Oracle has released security patches addressing this vulnerability as part of their September 2026 Critical Security Patch Update. Users are strongly advised to apply these patches promptly.