CVE-2026-112067

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Trending — 3 sources updated this week

Also known asEUVD-2026-104872 (ENISA EUVD) · GHSA-mf3p-7j87-6qr4 (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.9Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (TYPO3 Association) lists TYPO3 Extension "Accessible Form Captcha" versions 4.0.0 up to but not including 5.4.2 as affected. No release containing a fix is confirmed on record.

The extension hides the correct answer to each CAPTCHA inside the image data of the CAPTCHA itself. Anyone who can request a CAPTCHA image can read the answer from it and submit it, so automated clients can pass the challenge. This applies to the default configuration, because the audio feature that causes the answer to be embedded is enabled by default. Forms that rely on the CAPTCHA as their only protection against automated submissions are exposed to abuse by bots.

CVSS v3
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
46
EG Risk 46/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.the CNA's CVSS · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 20, 2026

Last Modified

October 24, 2026

Advisory Details (1)

Auto-updated Oct 20, 2026
No fix on record yet.
Web page

TYPO3-EXT-SA-2026-030: Captcha Bypass in extension "Accessible Form Captcha" (bw_captcha) - TYPO3 News

https://typo3.org/security/advisory/typo3-ext-sa-2026-030

Vendor Advisories for CVE-2026-112067(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 20× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-10-25 14:51 UTCEG score recompute
  7. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-24 07:35 UTCEG score recompute
  9. 2026-10-24 07:35 UTCGHSA enrichmentGHSA-mf3p-7j87-6qr4
  10. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-20 19:47 UTCEG score recompute
  14. 2026-10-20 19:47 UTCGHSA enrichmentGHSA-mf3p-7j87-6qr4
  15. 2026-10-20 19:17 UTCEG score recompute
  16. 2026-10-20 19:17 UTCGHSA enrichmentGHSA-mf3p-7j87-6qr4
  17. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-10-20 10:27 UTCEG score recompute
  19. 2026-10-20 09:39 UTCEG score recomputeFirst assessed: 6.9 MEDIUM
  20. 2026-10-20 09:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-112067?
CVE-2026-112067 is a medium-severity vulnerability; its CVE record was published on October 20, 2026. The extension hides the correct answer to each CAPTCHA inside the image data of the CAPTCHA itself. Anyone who can request a CAPTCHA image can read the answer from it and submit it, so automated clients can pass the challenge. This applies to the default configuration, because the audio feature…
When was CVE-2026-112067 made public?
CVE-2026-112067 was made public on October 20, 2026: that is the date its CVE record's CNA, TYPO3 Association, gives for when the vulnerability was made public. The CVE record itself was published on October 20, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-112067 actively exploited?
CVE-2026-112067 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-112067?
CVE-2026-112067 has a CVSS base score of 6.9 (the CNA's own assessment, by typo3; NVD's own analysis pending).
How do I remediate CVE-2026-112067?
No fix for CVE-2026-112067 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (TYPO3 Association) lists TYPO3 Extension "Accessible Form Captcha" versions 4.0.0 up to but not including 5.4.2 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-112067 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-112067

Explore →

Is Your Infrastructure Affected by CVE-2026-112067?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.