Secuno
ENNL
Book demo

CVE-2026-69223

Apache Allura server-side request forgery (SSRF)

9.1 CRITICALEPSS 0.78%
  1. Published11 Aug 2026

Description

Apache Allura's webhooks are vulnerable to Server-Side Request Forgery (SSRF). This issue affects Apache Allura: before 1.19.1. Users are recommended to upgrade to version 1.19.1, which fixes the issue.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Apache Allura< 1.19.1

Remediation

Fixed in
Apache Allura≥ 1.19.1

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-8911110.0
The SAP Cloud SDK for Python contains an OAuth2 SSRF vulnerability affecting…
CVE-2026-571438.8
PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.62,…
CVE-2026-1092388.6
Crawl4AI 0.7.0 before 0.9.4 contains a server-side request forgery vulnerability that…
CVE-2026-859528.5
Affected Linux-based Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x…
CVE-2026-859518.5
Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7…
CVE-2026-694359.6
Missing authorization in Azure SRE Agent allows an authorized attacker to elevate…

Frequently asked

Is CVE-2026-69223 being actively exploited?

CVE-2026-69223 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.78%.

How severe is CVE-2026-69223?

CVE-2026-69223 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.78% probability of exploitation.

Which products are affected by CVE-2026-69223?

Affected products include Apache Allura.

How do I fix CVE-2026-69223?

Upgrade affected software to a fixed version, for example Apache Allura 1.19.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-69223 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.