newrelic / newrelic/aws_s3_log_ingestion_lambda
Multiple CVEs in the aiohttp dependency
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
Hi New Relic team,
Our security scanning identified several CVEs affecting aiohttp in the New Relic log ingestion Lambda function. Could you please update the dependency and publish a new release containing a fixed version?
Affected CVEs:
CVE-2026-54275
CVE-2026-54280
CVE-2026-54274
CVE-2026-69244
CVE-2026-54279
CVE-2026-54277
CVE-2026-54273
CVE-2026-54278
CVE-2026-54276
CVE-2026-69243
CVE-2026-59881
Once a fixed release is available, we will update our deployed log ingestion applications.
Thanks for your help!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the dependency declaration and packaging or release entry point for the Python AWS Lambda project, then verify which aiohttp version resolves all listed CVEs. Done means a new release is published with the fixed dependency so deployed log-ingestion applications can update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- backend, cloud, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100