Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

Invenio-App vulnerable to host header injection attack

CVE-2019-1020006GHSA-94mf-xfg5-r247

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (invenio-app 1.1.1, 1.0.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI invenio-app

    Affected
    < 1.0.6>= 1.1.0, <= 1.1.0
    Fixed in
    1.0.6, 1.1.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N · score source
EPSS
  • CVE-2019-1020006: 0.93% estimated exploitation activity in the next 30 days; percentile 60.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

APPALLOWEDHOSTS not always preventing host header injection Impact A possible host header injection attack have been identified in Invenio-App. For an attack to be possible, all conditions below must be met: 1. Your webserver must have been configured to route all requests to your application. 2. You must have relied on APPALLOWEDHOSTS configuration variable to whitelist allowed host headers. 3. Flask's request.host must not have been evaluated during request handling. An example of a view which does not evalute request.host is a simple view using just urlfor to generate an external URL (similar is possible when rendering just a Jinja template): This happens, because Werkzeug's trusted host feature, which APPALLOWEDHOSTS rely on, does not check the the list of trusted hosts in it's routing system that urlfor is relying on. Patches Invenio-App v1.0.6 and v1.1.1 fully fix the issue. Note, we strongly recommend (see Securing your instance) that you never route requests to your…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-94mf-xfg5-r247

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-94mf-xfg5-r247

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-1020006

Advisory: Invenio-App vulnerable to host header injection attack
IDs: CVE-2019-1020006, GHSA-94mf-xfg5-r247
Record: https://patchnext.com/advisories/cve-2019-1020006 (revision 3, source checked 26 Oct 2026, 13:17 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: invenio-app 1.1.1, 1.0.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI invenio-app: affected < 1.0.6; >= 1.1.0, <= 1.1.0; fixed in 1.0.6, 1.1.1

## Suggested inspection (read-only)
- `python -m pip show invenio-app`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on invenio-app.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-94mf-xfg5-r247 (OSV record GHSA-94mf-xfg5-r247 lists affected ranges: PyPI invenio-app >=0 =1.1.0 <1.1.1 (fixed))
- Verified: https://github.com/advisories/GHSA-94mf-xfg5-r247 (GitHub-reviewed advisory GHSA-94mf-xfg5-r247 lists affected ranges: PyPI invenio-app >=0 =1.1.0 <=1.1.0)

Commands are suggestions: review each one before running it.

Loading voting…