{"items":[{"id":"NVI-00014008","kind":"vulnerability","title":"Apache Camel-Iggy: The inbound consumer maps externally-supplied Iggy message user-headers into the Exchange without a HeaderFilterStrategy","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-pw9q-pq7c-rfqw","CVE-2026-55994"],"plain_summary":"GitHub lists this reviewed advisory for org.apache.camel:camel-iggy, org.apache.camel:camel-iggy. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-6e2dea7d237e2006dcd57c05e5e9f0a6"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-08-28T20:09:39.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-304daad5bdd6e911268e6c0f88c5ae5b"},{"kind":"CVSS","as_of":"2026-07-09T03:03:31.657Z","value":"7.5 HIGH (3.1)","meaning":"134c704f-9b21-4f2e-91b3-4a467353bcc0 severity; no combined Null risk score.","source_id":"sr-6e2dea7d237e2006dcd57c05e5e9f0a6"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-304daad5bdd6e911268e6c0f88c5ae5b","url":"https://github.com/advisories/GHSA-pw9q-pq7c-rfqw","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-pw9q-pq7c-rfqw","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:58.521Z"},{"id":"sr-6e2dea7d237e2006dcd57c05e5e9f0a6","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55994","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-55994","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-08T01:48:33.286Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-304daad5bdd6e911268e6c0f88c5ae5b"],"technology":"org.apache.camel:camel-iggy","known_exclusions":[],"conditions_summary":"Improper Input Validation, Exposure of Sensitive Information to an Unauthorized Actor, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel in Iggy component.\n\nThe camel-iggy consumer mapped the user-headers of inbound Iggy messages into the Camel Exchange header map without applying any HeaderFilterStrategy (IggyFetchRecords copied the message user-headers straight into the Exchange). Because nothing blocked the Camel header namespace, an actor able to publish to the consumed Iggy stream/topic could set Camel-internal control headers - including CamelHttpUri (Exchange.HTTP_URI) - simply by supplying them as message user-headers. In a route where the Iggy consumer feeds a downstream HTTP producer, the injected CamelHttpUri redirects the server-side HTTP request to an attacker-chosen destination (server-side request forgery - for example to an internal service or a cloud metadata endpoint). In addition, the HTTP producer resolves Camel property placeholders on the resulting (attacker-controlled) URI, so placeholders embedded in the injected value - such as an environment-variable reference, an application property, or a vault reference - are resolved to their real values","public_affected_ranges":[">= 4.17.0, < 4.18.3"]},{"certainty":"source_listed","source_ids":["sr-304daad5bdd6e911268e6c0f88c5ae5b"],"technology":"org.apache.camel:camel-iggy","known_exclusions":[],"conditions_summary":"Improper Input Validation, Exposure of Sensitive Information to an Unauthorized Actor, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel in Iggy component.\n\nThe camel-iggy consumer mapped the user-headers of inbound Iggy messages into the Camel Exchange header map without applying any HeaderFilterStrategy (IggyFetchRecords copied the message user-headers straight into the Exchange). Because nothing blocked the Camel header namespace, an actor able to publish to the consumed Iggy stream/topic could set Camel-internal control headers - including CamelHttpUri (Exchange.HTTP_URI) - simply by supplying them as message user-headers. In a route where the Iggy consumer feeds a downstream HTTP producer, the injected CamelHttpUri redirects the server-side HTTP request to an attacker-chosen destination (server-side request forgery - for example to an internal service or a cloud metadata endpoint). In addition, the HTTP producer resolves Camel property placeholders on the resulting (attacker-controlled) URI, so placeholders embedded in the injected value - such as an environment-variable reference, an application property, or a vault reference - are resolved to their real values","public_affected_ranges":[">= 4.19.0, < 4.21.0"]}],"null_published_at":"2026-11-08T19:53:48.746Z","source_updated_at":"2026-08-28T20:09:39.000Z","source_disclosed_at":"2026-07-06T09:30:30.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-02T02:21:58.521Z"},{"id":"NVI-00014008","kind":"vulnerability","title":"Apache Camel-Iggy: The inbound consumer maps externally-supplied Iggy message user-headers into the Exchange without a HeaderFilterStrategy","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pw9q-pq7c-rfqw","CVE-2026-55994"],"plain_summary":"GitHub lists this reviewed advisory for org.apache.camel:camel-iggy, org.apache.camel:camel-iggy. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-304daad5bdd6e911268e6c0f88c5ae5b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-08-28T20:09:39.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-304daad5bdd6e911268e6c0f88c5ae5b"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-304daad5bdd6e911268e6c0f88c5ae5b","url":"https://github.com/advisories/GHSA-pw9q-pq7c-rfqw","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-pw9q-pq7c-rfqw","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:58.521Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-304daad5bdd6e911268e6c0f88c5ae5b"],"technology":"org.apache.camel:camel-iggy","known_exclusions":[],"conditions_summary":"Improper Input Validation, Exposure of Sensitive Information to an Unauthorized Actor, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel in Iggy component.\n\nThe camel-iggy consumer mapped the user-headers of inbound Iggy messages into the Camel Exchange header map without applying any HeaderFilterStrategy (IggyFetchRecords copied the message user-headers straight into the Exchange). Because nothing blocked the Camel header namespace, an actor able to publish to the consumed Iggy stream/topic could set Camel-internal control headers - including CamelHttpUri (Exchange.HTTP_URI) - simply by supplying them as message user-headers. In a route where the Iggy consumer feeds a downstream HTTP producer, the injected CamelHttpUri redirects the server-side HTTP request to an attacker-chosen destination (server-side request forgery - for example to an internal service or a cloud metadata endpoint). In addition, the HTTP producer resolves Camel property placeholders on the resulting (attacker-controlled) URI, so placeholders embedded in the injected value - such as an environment-variable reference, an application property, or a vault reference - are resolved to their real values","public_affected_ranges":[">= 4.17.0, < 4.18.3"]},{"certainty":"source_listed","source_ids":["sr-304daad5bdd6e911268e6c0f88c5ae5b"],"technology":"org.apache.camel:camel-iggy","known_exclusions":[],"conditions_summary":"Improper Input Validation, Exposure of Sensitive Information to an Unauthorized Actor, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel in Iggy component.\n\nThe camel-iggy consumer mapped the user-headers of inbound Iggy messages into the Camel Exchange header map without applying any HeaderFilterStrategy (IggyFetchRecords copied the message user-headers straight into the Exchange). Because nothing blocked the Camel header namespace, an actor able to publish to the consumed Iggy stream/topic could set Camel-internal control headers - including CamelHttpUri (Exchange.HTTP_URI) - simply by supplying them as message user-headers. In a route where the Iggy consumer feeds a downstream HTTP producer, the injected CamelHttpUri redirects the server-side HTTP request to an attacker-chosen destination (server-side request forgery - for example to an internal service or a cloud metadata endpoint). In addition, the HTTP producer resolves Camel property placeholders on the resulting (attacker-controlled) URI, so placeholders embedded in the injected value - such as an environment-variable reference, an application property, or a vault reference - are resolved to their real values","public_affected_ranges":[">= 4.19.0, < 4.21.0"]}],"null_published_at":"2026-11-02T10:00:37.196Z","source_updated_at":"2026-08-28T20:09:39.000Z","source_disclosed_at":"2026-07-06T09:30:30.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-02T02:21:58.521Z"}],"next_cursor":null,"snapshot_revision":"42594"}